-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.13
-
None
-
Moderate
-
No
-
False
-
Description of problem:
The annotation `target.workload.openshift.io/management: '{"effect": "PreferredDuringScheduling"}'` for the pod-identity-webhook deployment workload did not take effect.
That the YAML file specifies "annotation" as:
annotation:
target.workload.openshift.io/management: '{"effect": "PreferredDuringScheduling"}'
Perhaps in this situation,the field 'annotation' should be written as 'annotations', Like:
annotations:
target.workload.openshift.io/management: '{"effect": "PreferredDuringScheduling"}'
Version-Release number of selected component (if applicable):
registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-03-10-063231(An image that includes #PR520)
How reproducible:
always
Steps to Reproduce:
1.Install an OCP cluster with realse image: registry.ci.openshift.org/ocp/release:4.14.0-0.nightly-2023-03-10-063231 2.Check if annotation be add to pod-identity-webhook deployment.
Actual results:
$ oc describe deployment pod-identity-webhook -n openshift-cloud-credential-operator | grep 'target.workload.openshift.io/management' ###No result output.
Expected results:
$ kubectl describe deployment pod-identity-webhook -n openshift-cloud-credential-operator | grep 'target.workload.openshift.io/management'
Annotations: target.workload.openshift.io/management: {"effect": "PreferredDuringScheduling"}
Additional info:
I created a new Pod named "pod-identity-webhook-1" and deployed it in my local environment. Prior to deployment, I modified the "annotation" field in the YAML file as "annotations". After successful deployment, I noticed that the Pod was successfully added to the pod-identity-webhook Deployment.
$ oc describe deployment pod-identity-webhook-1 -n openshift-cloud-credential-operator | grep 'target.workload.openshift.io/management'
Annotations: target.workload.openshift.io/management: {"effect": "PreferredDuringScheduling"}