-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
CORS-3427: aws: custom security group: limit to 2 #50022
Conversation
@r4f4: This pull request references CORS-3427 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 bug to target the "4.16.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 openshift-eng/jira-lifecycle-plugin repository. |
With the Installer move to using CAPI/CAPA for provisioning, there are now 3 security groups created during install. With the limit of 5 per network interface, this leaves only 2 additional security groups.
4f66a1e
to
1b22788
Compare
[REHEARSALNOTIFIER]
A total of 60 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse pull-ci-openshift-installer-master-e2e-aws-custom-security-groups pull-ci-openshift-installer-master-altinfra-e2e-aws-custom-security-groups periodic-ci-openshift-openshift-tests-private-release-4.16-arm64-ec-aws-ipi-usertags-custom-sg-f14 |
/pj-rehearse pull-ci-openshift-installer-master-altinfra-e2e-aws-custom-security-groups |
/pj-rehease ack |
/assign @yunjiang29 |
/pj-rehearse ack |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon, r4f4 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 |
2d0b15c
into
openshift:master
@r4f4: 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. |
With the Installer move to using CAPI/CAPA for provisioning, there are now 3 security groups created during install. With the limit of 5 per network interface, this leaves only 2 additional security groups.