-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(manager): set machinepool true as default #5146
refactor(manager): set machinepool true as default #5146
Conversation
|
Welcome @KOREAN139! |
Hi @KOREAN139. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 kubernetes-sigs/prow repository. |
/ok-to-test |
/retest |
1 similar comment
/retest |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5146 +/- ##
=======================================
Coverage 51.36% 51.36%
=======================================
Files 273 273
Lines 24676 24676
=======================================
Hits 12674 12674
Misses 11212 11212
Partials 790 790 ☔ View full report in Codecov by Sentry. |
Thanks @KOREAN139 – we had #4911 but it was never updated. Could you make a similar change to
|
/retest |
Just updated following documents.
Let me know if there's any document left to update! @mboersma P.S. Force-pushed some commits to make it verified / fix some commit messages 😅 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just a minor wording change and remember to squash your commits!
- MachinePool feature flag is true as default since CAPI v1.7.0, but capz-contoller-manager deployment still uses false as default. - It causes error `spec: Forbidden: can be set only if the Cluster API 'MachinePool' feature flag is enabled` when user does not specify MachinePool feature flag true in capz-controller-manager. - As CAPI v1.7.0 has been GA around six months, It should set MachinePool feature flag as true to make seamless UX. references https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.7.0 kubernetes-sigs/cluster-api#10141 refactor(hack): set machinepool true in default - set machinepool feature flag as true for controller in observability hack stack doc(machinepool): add note of enabled per default - add note about MachinePool feature gate's promotion to beta - add note about MachinePool feature gate's default value (true) doc(machinepool): restore feature requirement part - as the information "MachinePool feature gate need to be set as true" must be shown, restore the part - modify the "need to turn on" sentence to "it's already on, but you can set it again" doc(machinepool): accept wording change - changed the wording as willie-yao suggested in PR Co-authored-by: Willie Yao <[email protected]>
Just applied your suggestion, and squashed commits @willie-yao ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thank you!
LGTM label has been added. Git tree hash: a2b5271f712e6f3e026971ccf546a5722fdcdebb
|
🚢 it! |
/lgtm Thank you! 🚀 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: willie-yao The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
spec: Forbidden: can be set only if the Cluster API 'MachinePool' feature flag is enabled
when user does not specify MachinePool feature flag true in capz-controller-manager.EXP_MACHINE_POOL
.references
https://github.com/kubernetes-sigs/cluster-api/releases/tag/v1.7.0
kubernetes-sigs/cluster-api#10141
related slack thread
https://kubernetes.slack.com/archives/CEX9HENG7/p1727200579137939
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Closes #4911
Special notes for your reviewer:
TODOs:
Release note: