chore: remove AWSServiceLBNetworkSecurityGroup feature gate - #2974
Conversation
The AWSServiceLBNetworkSecurityGroup feature gate has been enabled by default across all profiles and feature sets, making it redundant. Remove the gate definition and regenerate payload manifests.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Skipping CI for Draft Pull Request. |
|
Hello @damdo! Some important instructions when contributing to openshift/api: |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (11)
💤 Files with no reviewable changes (10)
📝 WalkthroughWalkthroughRemoved the 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary
AWSServiceLBNetworkSecurityGroupfeature gate fromfeatures/features.go— it has been enabled by default across all profiles and feature sets and is no longer neededfeaturegate-test-analyzer_test.goto use a different AWS gate (AWSClusterHostedDNS)Test plan
make test-unitpasses (includingTestOKDHasAllDefaultFeatureGates)hack/verify-payload-featuregates.shpassesAWSServiceLBNetworkSecurityGroupin the codebase