-
Notifications
You must be signed in to change notification settings - Fork 3
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
Docs #25
base: main
Are you sure you want to change the base?
Conversation
foot
commented
Nov 24, 2023
•
edited
Loading
edited
- Add some user docs
- Upgrade to helmify 4.10 which includes support for annotating Service Accounts
- link out to CAPI quickstart
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.
This looks great so far!
> [!NOTE] | ||
> AWS uses the term "labels", here we'll use "tags" to refer to both AWS labels and Azure tags. | ||
|
||
Any tags you add to your AKS/EKS clusters will be added as labels to the `GitopsCluster` resource. This is useful to tie into other components like the cluster bootstrap controller and the GitOpsSets controller. These controllers use labels to determine which clusters to act upon. |
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.
Can we link to docs for these controllers?
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.
Yes, that would be neat. Ideally we want to be able to copy these instruction over the public facing site pretty verbatim which makes linking tricky.
Thinking..
|
||
The steps are roughly: | ||
|
||
- Create an IAM Policy that can list EKS clusters and get kubeconfigs. |
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.
Can we link to these, provide more detail?
|
||
Its often used to run `flux bootstrap` on a new cluster to install flux and connect it to a Git Repository. | ||
|
||
EXAMPLE |
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.
I think it's ok to link out to this, https://docs.gitops.weave.works/docs/cluster-management/managing-clusters-without-capi/#add-a-cluster-bootstrap-config ?
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.
Yep good one
|
||
If we tag our AKS/EKS cluster with `wego-admin-rbac: enabled` in the Azure portal or AWS Console, then the Cluster Reflector will create a GitopsCluster with that label. | ||
|
||
We can then create a GitOpsSet that will generate a Kustomization for each cluster with the label `wego-admin-rbac: enabled`. |
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.
I've tended to mark names of CRs as code
so that it's clear that it's a specific thing, so here GitOpsSet
and Kustomization
.
Co-authored-by: Kevin McDermott <[email protected]>
Co-authored-by: Kevin McDermott <[email protected]>