-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-17733: [release-4.13] remove shared VPC cred request #972
OCPBUGS-17733: [release-4.13] remove shared VPC cred request #972
Conversation
Backporting credential requests has the potential of breaking upgrades, specifically if clusters are running in mint mode and have removed the root credentials during z-stream upgrades. This commit removes the 4.13 bump to the cred request for the AWS shared VPC feature. The rest of the feature remains intact so that it can be utilized by managed services which does not depend on credential requests.
/assign @gcs278 |
/retitle OCPBUGS-17733: [release-4.13] remove shared VPC cred request |
/jira refresh |
@patrickdillon: No Jira issue is referenced in the title of this pull request. 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. |
@patrickdillon: This pull request references Jira Issue OCPBUGS-17733, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
We will need to override this, as this bug is directly applicable to 4.13. There is no 4.14 bug. |
|
Thanks for this fix. Sounds like we are all on the same page with reverting this change. Will still need someone to apply |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gcs278 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:
Approvers can indicate their approval by writing |
#966 added the |
e2e-aws-ovn failed, but the error is unrelated to the changes in this PR. |
/override ci/prow/e2e-aws-ovn |
@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-aws-ovn 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. |
@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-aws-ovn 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. |
@patrickdillon: Jira Issue OCPBUGS-17733: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-17733 has been moved to the MODIFIED state. 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. |
@patrickdillon: The following test failed, say
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/test-infra repository. I understand the commands that are listed here. |
Fix included in accepted release 4.13.0-0.nightly-2023-08-24-052924 |
Backporting credential requests has the potential of breaking upgrades, specifically if clusters are running in mint mode and have removed the root credentials during z-stream upgrades.
This commit removes the 4.13 bump to the cred request for the AWS shared VPC feature. The rest of the feature remains intact so that it can be utilized by managed services which does not depend on credential requests.