bootstrap: Pass rendered manifests and payload version to etcd render#10679
bootstrap: Pass rendered manifests and payload version to etcd render#10679sanchezl wants to merge 1 commit into
Conversation
Add --rendered-manifest-files and --payload-version flags to the etcd-render invocation in bootkube.sh so the cluster-etcd-operator render command can read the FeatureGate CR from pre-rendered manifests instead of parsing feature gates from the raw install-config. The api-render step already runs before etcd-render and produces the fully-resolved FeatureGate CR in /assets/manifests/, so the manifests are guaranteed to be available. This aligns etcd-render with the pattern used by kube-apiserver-render, kube-controller-manager-render, and config-render, all of which already pass these flags. Requires a coordinated cluster-etcd-operator change to accept the new flags.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
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 (1)
📝 WalkthroughWalkthroughThe etcd bootstrap script now passes a rendered-manifest destination and payload version to ChangesEtcd bootstrap rendering
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 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 |
|
@sanchezl: all tests passed! 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. |
|
/cc openshift/cluster-etcd-operator#1648 must go in first before we can test and merge this change. Otherwise, |
Summary
Add
--rendered-manifest-filesand--payload-versionflags to the etcd-render invocation inbootkube.shso the cluster-etcd-operator render command can read the FeatureGate CR from pre-rendered manifests.Background
The
api-renderstep already runs beforeetcd-renderand produces the fully-resolved FeatureGate CR (withfeatureSetexpanded into individual gates) in/assets/manifests/. The etcd-render step was the only operator render that didn't consume these manifests — it parsed feature gates from the raw install-config instead, which missedfeatureSetresolution.This aligns the etcd-render invocation with the pattern already used by
kube-apiserver-render,kube-controller-manager-render, andconfig-render, all of which pass--rendered-manifest-files=/assets/manifestsand--payload-version=$VERSION.Coordinated change
Requires openshift/cluster-etcd-operator#1648 to accept the new flags. Both PRs must land in the same payload.
Test plan
Summary by CodeRabbit