🌱 Add AndiDog as machine pool area reviewer #13033
Open
+1
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
As discussed in office hours, the machine pool area should have more contributors overall, and adding someone with a reviewer role could lead to improving this situation.
In my job, I regularly work on CAPA machine pool support, and therefore also worked on the generic parts in CAPI. Overall, there were probably more than contributed 10 PRs relating to that area. I've been a CAPA maintainer since 2024-07, reviewer since 2023-12. My work included major features such as AWSMachinePool machines support (CAPA) or MachineHealthCheck remediation support for machine pool machines (CAPI; pending review by the working group). I'm in office hours somewhat regularly and try to discuss important topics – until now particularly topics around machine pool API, contract and expected behavior (example from ~2023: how/whether to roll machine pool machines on
KubeadmConfigchanges). I've worked on, or looked into, the machine pool and machine controller codebase often enough to be pretty familiar.My current goal as reviewer would be to help the working group stabilize and document the API and contract well, then later add or fix reasonable features.