oc Annotate Examples¶
Introduction¶
Declarative and metadata commands change OpenShift objects. Use dry-run or diff when possible, then verify the exact field changed.
When You Need This Command¶
Use this command when you need to inspect, change, or verify OpenShift resources from the terminal without relying on the web console.
Syntax¶
oc <command> <resource> [name] -n <project>
Practical Examples¶
oc label deployment web tier=frontend -n app
oc annotate deployment web owner=platform -n app
oc patch deployment web -n app --type=merge -p '{"spec":{"replicas":3}}'
oc get deployment web -n app --show-labels
Example output:
deployment.apps/web labeled
deployment.apps/web annotated
deployment.apps/web patched
Verification¶
oc get deployment web -n app --show-labels
oc describe deployment web -n app
Common Mistakes¶
- Patching production objects without saving the previous YAML.
- Using labels that break service selectors.
- Deleting resources without checking owner references.
Production Notes¶
Run read-only commands first, check the active project, and prefer declarative manifests for repeatable changes.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
Summary¶
oc Annotate Examples is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.