Revert "CCO-421: *: split pod identity webhooks from core controller" #605
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@dgoodwin: This pull request references CCO-421 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. In response to this:
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/test-infra repository. |
1 similar comment
|
@dgoodwin: This pull request references CCO-421 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. In response to this:
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/test-infra repository. |
|
/close Doubled with #604 |
|
@dgoodwin: Closed this PR. In response to this:
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/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dgoodwin The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Reverts #592
Change unfortunately is full failing upgrade jobs on CI payload, likely on nightly payload shortly.
To re-introduce please unrevert this revert, layer in separate commit with fixes, and confirm success with
/payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgradeTRT-1299 has details on what I suspect may have gone wrong, it looks like the metrics endpoint is not on the right container perhaps.