NE-2569: Promote Dynamic Configuration Manager to Default#2788
NE-2569: Promote Dynamic Configuration Manager to Default#2788Miciah wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Skipping CI for Draft Pull Request. |
|
Hello @Miciah! Some important instructions when contributing to openshift/api: |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Promote the IngressControllerDynamicConfigurationManager featuregate to the Default featureset. This commit resolves NE-2569. https://redhat.atlassian.net/browse/NE-2569 * features/features.go: Promote the featuregate to Default. * features.md: * operator/v1/zz_generated.crd-manifests/*: * payload-manifests/featuregates/*: Regenerate.
|
[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 |
cd8658e to
52fb33c
Compare
|
@Miciah: This pull request references NE-2569 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 story to target the "4.22.0" version, but no target version was set. DetailsIn 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. |
|
/jira refresh |
|
@Miciah: This pull request references NE-2569 which is a valid jira issue. DetailsIn 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. |
|
/test lint |
|
PR-Agent: could not fine a component named |
|
/assign |
|
/assign @jcmoraisjr |
|
openshift/origin#30926 is merged: |
|
Buried in the output is 0% passing on IPv6 clusters - openshift/origin#30972 should fix. |
|
I did the math you'll need 228 consecutive passes on metal IPv6 to get it back to 95% 😓 That's only ~114 test runs a day to get it in for Friday Branch Cut. That means you'll need to kick a test off every ~13 minutes (just kidding, don't do that). @Miciah @jcmoraisjr Anyways, just a heads up, you'll likely have to advocate for an exception to get this in before branch cut. |
|
/test verify-feature-promotion |
|
PR-Agent: could not fine a component named |
Review Summary by QodoPromote IngressControllerDynamicConfigurationManager featuregate to Default
WalkthroughsDescription• Promote IngressControllerDynamicConfigurationManager featuregate to Default • Move feature from TechPreview to Default and OKD featuresets • Update feature documentation and manifest files accordingly • Regenerate CRD manifests to reflect new feature status Diagramflowchart LR
A["IngressControllerDynamicConfigurationManager<br/>Feature Gate"] -->|"Promote from<br/>TechPreview"| B["Default Featureset"]
A -->|"Add to"| C["OKD Featureset"]
B -->|"Update"| D["Feature Documentation"]
C -->|"Update"| D
D -->|"Regenerate"| E["Manifest Files"]
File Changes1. features/features.go
|
Code Review by Qodo
|
|
@qodo-code-review,
The featuregate will be enabled by default, but the feature will be off by default as it is an experimental feature. Enabling the featuregate just enables the cluster-admin to enable the feature by explicitly setting the new API field. |
|
@Miciah: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Promote the IngressControllerDynamicConfigurationManager featuregate to the Default featureset.
This PR depends on openshift/origin#30926.