-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Proactive Architecture
-
False
-
None
-
False
-
-
-
Installer Sprint 256, Installer Sprint 257, Installer (PB) Sprint 258, Installer (PB) Sprint 259
User Story:
Once a cloud provider uses CAPI by default, the feature gate it used becomes tech debt.
Acceptance Criteria:
Description of criteria:
- openshift/api PR removing the feature gate
- remove feature gate conditionals from the installer
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.
- links to
(5 links to)
[CORS-3582] Remove feature gates for providers that use CAPI by default
It's not clear when we'll be able to remove the feature gates from openshift/api. Anyway the Installer doesn't check the feature gates for platforms where CAPI is the default, so installs should work even when using CustomNoUpgrade feature set.
o/api PR merged. There is no need to bump the o/api version in the Installer because the installer is already ignoring feature gates for capi providers. It'll pick up the o/api changes when it's bumped for something else.