render: Remove install-config feature gate fallback#1649
Conversation
WalkthroughRendering now requires rendered manifest paths and a payload version, reads FeatureGate resources from manifests, and derives feature sets through a payload-versioned accessor. Tests generate corresponding manifests, including custom PKI coverage. ChangesManifest-based FeatureGate rendering
Estimated code review effort: 3 (Moderate) | ~25 minutes Sequence Diagram(s)sequenceDiagram
participant newTemplateData
participant getFeatureGatesFromManifests
participant readFeatureGate
participant renderedManifests
newTemplateData->>getFeatureGatesFromManifests: request feature sets
getFeatureGatesFromManifests->>readFeatureGate: scan rendered manifest paths
readFeatureGate->>renderedManifests: read FeatureGate YAML or JSON
renderedManifests-->>readFeatureGate: return FeatureGate resource
readFeatureGate-->>getFeatureGatesFromManifests: return FeatureGate object
getFeatureGatesFromManifests-->>newTemplateData: return enabled and disabled feature sets
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/lgtm |
|
Scheduling required tests: |
Now that the installer passes --rendered-manifest-files and --payload-version to the etcd-render invocation, remove the install-config feature gate parsing fallback and make both flags required. This removes getFeatureGatesFromInstallConfig and the getFeatureGates dispatcher, leaving only the standard FeatureGate CR path.
ef85c95 to
042318e
Compare
|
New changes are detected. LGTM label has been removed. |
|
[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 |
|
@sanchezl: The following tests 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. |
|
/hold for openshift/installer#10679 |
|
Reminder for myself to check e2e-aws-ovn-pki-rsa-techpreview to make sure this still passes without the fallback. |
Summary
Remove the install-config feature gate parsing fallback now that openshift/installer#10679 passes
--rendered-manifest-filesand--payload-versionto the etcd-render invocation.This makes both flags required and removes
getFeatureGatesFromInstallConfig()and thegetFeatureGates()dispatcher, leaving only the standard FeatureGate CR path viagetFeatureGatesFromManifests().Depends on
#1648 — render: Read FeatureGate CR from rendered manifests(merged)This PR should merge after the installer dependency has landed.
Test plan
go test ./pkg/cmd/render/— all tests passgo vet ./pkg/cmd/render/— cleanSummary by CodeRabbit
FeatureGatemanifests included in rendered outputs.FeatureGateresources directly (from either files or directories) and validates that feature-gate data can be determined.FeatureGatemanifests.