-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Future Sustainability
-
True
-
- Waiting for linked blockers (managed SG, bug fix on CLB BYO SG,)
- Need to investigate if the proposal won't require additional AWS permissions to the upstream CI
-
False
-
None
-
13
-
None
-
None
-
None
User Story:
As an OpenShift Engineer I want CCM-AWS upstream (NLB SG): isolate BYO SG from main implementation of managed SG so break down the feature enhance review lowering the amount of changes to the mainstream PR.
Description:
This is a tracking card to implement the BYO SG support on CCM.
Currently it was implemented on top of managed SG[1], but changes are crossing with bugs, and would be nice to have after the bug fix affecting CLB[2].
A code tracking has been created to the fork[3] with working code implementing during managed SG implementation - isolated from[1]. It is nice to have after [1]and [2].
[1] https://github.com/kubernetes/cloud-provider-aws/pull/1158
[2] https://github.com/kubernetes/cloud-provider-aws/pull/1209
[3] https://github.com/mtulio/openshift-cloud-provider-aws/pull/2
Acceptance Criteria:
< Record how we'll know we're done >
Other Information:
< Record anything else that may be helpful to someone else picking up the card >
issue created by splat-bot
- is blocked by
-
SPLAT-2311 [AWS NLB SG]: CCM Bug track <https://github.com/kubernetes/cloud-provider-aws/issues/1208> (CLB SG leak, blocks NLB BYO SG feat)
-
- To Do
-
-
-
- Closed
-
- is related to
-
-
- Closed
-