Skip to content
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

Document gitops deployment for Cluster API #8479

Closed
killianmuldoon opened this issue Apr 5, 2023 · 7 comments · Fixed by #10293
Closed

Document gitops deployment for Cluster API #8479

killianmuldoon opened this issue Apr 5, 2023 · 7 comments · Fixed by #10293
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@killianmuldoon
Copy link
Contributor

There's been a number of requests in the community lately about information for gitops deployment of Cluster API - for both the management cluster and workload clusters. We currently don't have info in the book about this, but it would be useful to provide at least a basic set-up guide so people know how to generate manifests and get up and running with Cluster API in gitops.

There's a couple of resources out there, but it would be great to get contributions from members of the community who have experience setting up CAPI that way.

/help
/kind documentation

@k8s-ci-robot
Copy link
Contributor

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

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to this:

There's been a number of requests in the community lately about information for gitops deployment of Cluster API - for both the management cluster and workload clusters. We currently don't have info in the book about this, but it would be useful to provide at least a basic set-up guide so people know how to generate manifests and get up and running with Cluster API in gitops.

There's a couple of resources out there, but it would be great to get contributions from members of the community who have experience setting up CAPI that way.

/help
/kind documentation

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.

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 5, 2023
@fabriziopandini
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 Apr 5, 2023
@dtzar
Copy link
Contributor

dtzar commented Apr 5, 2023

/assign

Discussion on the community call 4/5.

I think the focus should be on the higher-level architecture for the E2E scenario including workload cluster hydration, but to not get into specifics of implementation details - only linking to outside sources.

One relevant area where I do think could use deeper guidance is how to run a production CAPI management control plane. This may not be a part of this article, but linked to it.

@killianmuldoon
Copy link
Contributor Author

Thanks for taking this on @dtzar - I think the important thing with these docs is to have a place to start and to be able to point interested people in the right direction. Once we have something like that in place I think the gaps, those we can reasonably fill in the CAPI book and those we can't, will become a bit clearer.

@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Apr 5, 2024
@sbueringer
Copy link
Member

/triage accept
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Apr 5, 2024
@sbueringer
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 Apr 5, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment from k8s-ci-robot Apr 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants