CORS-4534: UPSTREAM: <carry>: Enable MachineTaintPropagation feature gate#303
Conversation
WalkthroughThe controller-manager feature-gates argument is extended in two manifest locations to include ChangesFeature gate patch update
Estimated code review effort: 1 (Trivial) | ~2 minutes Related PRs: None identified. Suggested labels: None Suggested reviewers: None 🐰 A tiny gate swings open wide, 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@openshift/patches/enable-metadata-syncing.yaml`:
- Line 15: Restore the default for MachineSetPreflightChecks in the
feature-gates string used by enable-metadata-syncing.yaml; the change should
only introduce MachineTaintPropagation and must not alter
EXP_MACHINE_SET_PREFLIGHT_CHECKS. Update the existing --feature-gates entry so
MachineSetPreflightChecks keeps its prior default in the controller-manager
configuration, using the same feature-gates list and symbols already present.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 96d3d4f7-7c97-4188-b147-071dc2d45fc0
📒 Files selected for processing (1)
openshift/patches/enable-metadata-syncing.yaml
|
/test e2e-hypershift |
|
/cc @nrb |
|
/retest |
|
Looks like hypershift has failed 3/3 runs; 2 of them had a bunch of First run with such failures Second run with such failures |
|
/test e2e-hypershift |
1 similar comment
|
/test e2e-hypershift |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo, tthvo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/verified by @tthvo |
|
@tthvo: This PR has been marked as verified by 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. |
|
/retitle CORS-4534: UPSTREAM: : Enable MachineTaintPropagation feature gate |
|
@tthvo: This pull request references CORS-4534 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 e2e-vsphere-staticip-ipam-ovn |
1 similar comment
|
/test e2e-vsphere-staticip-ipam-ovn |
|
/retest-required |
|
/retest-required |
1 similar comment
|
/retest-required |
|
@tthvo: 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. |
Description
Enable
MachineTaintPropagationfeature gate on CAPI controllers. This is a requirement for edge compute pool (AWS local and wavelength zones).See openshift/installer#10625
Summary by CodeRabbit