OSDOCS-21516: Fix spire server label selector in zero trust verification comm…

[Martande8055]

Version(s):
4.18, 4.19, 4.20, 4.21, 4.22, 5.0

Issue:
https://redhat.atlassian.net/browse/OSDOCS-21516

Link to docs preview:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/security_and_compliance/zero-trust-workload-identity-manager#zero-trust-manager-spire-server-config_zero-trust-manager-configuration

QE review:

• QE has approved this change.

Additional information:
This PR fixes an incorrect label selector in the SPIRE server verification section (zero-trust-manager-spire-server-config module):

• Updated the label selector in verification commands from app.kubernetes.io/name=server to app.kubernetes.io/name=spire-server. The previous label returned No resources found in zero-trust-workload-identity-manager namespace. when executed.

[openshift-ci-robot]

@Martande8055: This pull request references OSDOCS-21516 which is a valid jira issue.

Details

In response to this:

Version(s):
4.18, 4.19, 4.20, 4.21, 4.22, 5.0

Issue:
https://redhat.atlassian.net/browse/OSDOCS-21516

Link to docs preview:
https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/security_and_compliance/zero-trust-workload-identity-manager#zero-trust-manager-spire-server-config_zero-trust-manager-configuration

QE review:

• QE has approved this change.

Additional information:
This PR fixes an incorrect label selector in the SPIRE server verification section (zero-trust-manager-spire-server-config module):

• Updated the label selector in verification commands from app.kubernetes.io/name=server to app.kubernetes.io/name=spire-server. The previous label returned No resources found in zero-trust-workload-identity-manager namespace. when executed.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @Martande8055. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.