DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup support BYO SG for NLB #107
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@mtulio: This pull request references SPLAT-2113 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 spike to target the "4.19.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. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
mtulio
changed the title
mtulio
changed the title
mtulio
force-pushed
the
SPLAT-2113
branch
8 times, most recently
from
553c27d to
6ed5ae5
Compare
Introduce support of NLB provisioning with Security Groups when the following annotation matches: - service.beta.kubernetes.io/aws-load-balancer-manage-security-group: managed SG (CCM creates Security Group): - service.beta.kubernetes.io/aws-load-balancer-security-groups and service.beta.kubernetes.io/aws-load-balancer-extra-security-groups: unmanaged Security Group (CCM will not create or manage rules)
DNM - PR spike used to build images with cluster bot as local build isn't working as expected.