OCPBUGS-63233: Manual feature backport of cert rotation for whereabouts

[bpickard22]

Includes cert check script logic and delpoyment of token watcher daemonset in openshift-mutlus namespace to watch for token change

(cherry picked from commit d4fd19f)

[bpickard22]

/retest-required

[yingwang-0320]

/verified by "pre-merge testing"

[openshift-ci-robot]

@yingwang-0320: This PR has been marked as verified by "pre-merge testing".

In response to this:

/verified by "pre-merge testing"

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.

[bpickard22]

/retest-required

[bpickard22]

/retest-required

[bpickard22]

/retest-required

[bpickard22]

/retest-required

[pliurh]

/re-titile OCPBUGS-63233: Manual feature backport of cert rotation for whereabouts

[pliurh]

/re-title OCPBUGS-63233: Manual feature backport of cert rotation for whereabouts

[pliurh]

/retitle OCPBUGS-63233: Manual feature backport of cert rotation for whereabouts

[openshift-ci-robot]

@bpickard22: This pull request references Jira Issue OCPBUGS-63233, which is invalid:

• expected Jira Issue OCPBUGS-63233 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Includes cert check script logic and delpoyment of token watcher daemonset in openshift-mutlus namespace to watch for token change

(cherry picked from commit d4fd19f)

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.

[pliurh]

/retest-required

[pliurh]

/jira refresh

[openshift-ci-robot]

@pliurh: This pull request references Jira Issue OCPBUGS-63233, which is invalid:

• expected dependent Jira Issue OCPBUGS-58047 to target a version in 4.17.0, 4.17.z, but it targets "4.18.z" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[pliurh]

/jira refresh

[openshift-ci-robot]

@pliurh: This pull request references Jira Issue OCPBUGS-63233, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.z) matches configured target version for branch (4.16.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-58066 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-58066 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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.

[pliurh]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bpickard22, pliurh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pliurh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pliurh]

/retest-required

[openshift-ci]

@bpickard22: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-live-migration-sdn-ovn-rollback	ec7b717	link	false	/test e2e-aws-live-migration-sdn-ovn-rollback
ci/prow/e2e-aws-ovn-serial	ec7b717	link	false	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-hypershift-ovn-kubevirt	ec7b717	link	false	/test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-aws-sdn-upgrade	ec7b717	link	false	/test e2e-aws-sdn-upgrade
ci/prow/security	ec7b717	link	false	/test security
ci/prow/e2e-aws-live-migration-sdn-ovn	ec7b717	link	true	/test e2e-aws-live-migration-sdn-ovn
ci/prow/e2e-aws-ovn-windows	ec7b717	link	true	/test e2e-aws-ovn-windows

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.