DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup feature gate

[mtulio]

Draft for spike EP for NLB SGs on CIO on install time.

Related to:

• https://issues.redhat.com/browse/OCPSTRAT-1553
• SPLAT-2137
• SPLAT-2137: initial EP describing options openshift-splat-team/enhancements#1
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup feature gate #2299
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup cluster-ingress-operator#1224
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup installer#9681
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup support BYO SG for NLB cloud-provider-aws#107

[openshift-ci-robot]

@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.

Details

In response to this:

Draft for spike EP for NLB SGs on CIO on install time.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

Hello @mtulio! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mtulio
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

@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.

Details

In response to this:

Draft for spike EP for NLB SGs on CIO on install time.

Related to:

• https://issues.redhat.com/browse/OCPSTRAT-1553
• SPLAT-2137
• SPLAT-2137: initial EP describing options openshift-splat-team/enhancements#1
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup support BYO SG for NLB cloud-provider-aws#107
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup cluster-ingress-operator#1224
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup installer#9681

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-robot]

@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.

Details

In response to this:

Draft for spike EP for NLB SGs on CIO on install time.

Related to:

• https://issues.redhat.com/browse/OCPSTRAT-1553
• SPLAT-2137
• SPLAT-2137: initial EP describing options openshift-splat-team/enhancements#1
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup feature gate #2299
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup cluster-ingress-operator#1224
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup installer#9681
• DNM/SPLAT-2113: spike aws/CIO/IngressNLBSecurityGroup support BYO SG for NLB cloud-provider-aws#107

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-merge-robot]

PR needs rebase.

Details

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.

[openshift-ci]

@mtulio: 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-serial-1of2	bc9cb90	link	true	/test e2e-aws-serial-1of2
ci/prow/e2e-aws-serial-techpreview-1of2	bc9cb90	link	true	/test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-aws-serial-techpreview-2of2	bc9cb90	link	true	/test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-serial-2of2	bc9cb90	link	true	/test e2e-aws-serial-2of2

Full PR test history. Your PR dashboard.

Details

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.

[mtulio]

Closing as Won't Do as the approach will be changing the CCM to support SG when Service type-LoadBalancer NLB when cloud-config is enabled (enforced by CCCMO).

No CIO changes will be required using that approach.

See SPLAT-2253 and enhancement SPLAT-2187 for more details.