Skip to content

Tracking issue for v1Beta2 - MachinePools #12178

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.

Sign up for GitHub

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

Jump to bottom
Open
13 tasks
richardcase opened this issue May 9, 2025 · 3 comments
Open
13 tasks

Tracking issue for v1Beta2 - MachinePools #12178

richardcase opened this issue May 9, 2025 · 3 comments
Assignees
@mboersma @richardcase
Labels
area/api Issues or PRs related to the APIs area/machinepool Issues or PRs related to machinepools kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@richardcase
Copy link
Member

richardcase commented May 9, 2025 •
edited
Loading

This is to track the v1beta2 changes for machine pools and is an extension of the other v1beta2 work being tracked on #11947

From proposal

  • Disambiguate the usage of the ready term by renaming fields used for the initial provisioning workflow - ⚠️ Add initialization to MachinePool Status #12102 - Matt to confirm
  • Update ReadyReplicas counter to use the same semantic Machine's Ready condition and add missing UpToDateReplicas - ⚠️ Promote v1beta2 conditions #12066 - Matt to confirm
  • Align MachinePools replica counters to other CAPI resources - Rich
  • Remove FailureReason and FailureMessage to get rid of the confusing concept of terminal failures - Matt to confirm
  • Transition to new, improved, K8s API conventions aligned conditions

From parent issue

Other things

/area machinepool
/area api
@k8s-ci-robot k8s-ci-robot added area/machinepool Issues or PRs related to machinepools area/api Issues or PRs related to the APIs needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 9, 2025
@richardcase
Copy link
Member Author

/priority important-soon
/assign
/assign mboersma

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates an issue lacks a `priority/foo` label and requires one. labels May 9, 2025
@fabriziopandini
Copy link
Member

fabriziopandini commented May 9, 2025 •
edited
Loading

If you all agree I would add to the tracking issue the work for implementing a page for MP contract documentation under https://cluster-api.sigs.k8s.io/developer/providers/contracts/overview

note: we have something under https://cluster-api.sigs.k8s.io/developer/core/controllers/machine-pool but this is the wrong place, and also we should align the documentation to what has been done e.g. for https://cluster-api.sigs.k8s.io/developer/providers/contracts/infra-machine (or other contracts)

The main advantage is that this could help to start consolidating the knowledge about various MP incantations that exists and their implications in core Cluster API thus avoiding discussion/issues like e.g. #12164 (comment)

@chrischdi chrischdi added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label May 14, 2025
@k8s-ci-robot k8s-ci-robot removed the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label May 14, 2025
@chrischdi
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mboersma mboersma

@richardcase richardcase

Labels
area/api Issues or PRs related to the APIs area/machinepool Issues or PRs related to machinepools kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mboersma @richardcase @chrischdi @fabriziopandini @k8s-ci-robot