Cluster-api: [docs] Add controller architecture docs for MachinePool

Created on 24 Jun 2020  路  13Comments  路  Source: kubernetes-sigs/cluster-api

We should add a page for MachinePool in the architecture/controllers section of the book to document the controller flow for MachinePools, similar to https://cluster-api.sigs.k8s.io/developer/architecture/controllers/machine.html and https://cluster-api.sigs.k8s.io/developer/architecture/controllers/control-plane.html.

/kind documentation
/help

help wanted kindocumentation prioritbacklog

All 13 comments

@CecileRobertMichon:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

We should add a page for MachinePool in the architecture/controllers section of the book to document the controller flow for MachinePools, similar to https://cluster-api.sigs.k8s.io/developer/architecture/controllers/machine.html and https://cluster-api.sigs.k8s.io/developer/architecture/controllers/control-plane.html.

/kind documentation
/help

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/test-infra repository.

/milestone v0.3.x

I believe this is not taken by anyone :D

So, can I work on this?

Go for it!

cc @CecileRobertMichon @juan-lee

/lifecycle active
Sure, the proposal is a good starting point; the actual implementation of the code is https://github.com/kubernetes-sigs/cluster-api/tree/master/exp/controllers to be documented is here

/lifecycle active
Sure, the proposal is a good starting point; the actual implementation of the code is https://github.com/kubernetes-sigs/cluster-api/tree/master/exp/controllers to be documented is here

Thanks @fabriziopandini . I will look into it

/assign @shreyasbapat

Let me know if you need any guidance! I can also help review once you have a draft.

/milestone v0.4.0

Let's pair this task with taking MachinePool out of experiments

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

/remove-lifecycle stale
@shreyasbapat any update on this?

/priority backlog

/assign

Was this page helpful?
0 / 5 - 0 ratings