-
Notifications
You must be signed in to change notification settings - Fork 106
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
Added kkp-management via argocd tutorial #1723
base: main
Are you sure you want to change the base?
Conversation
CC @toschneck |
/assign toschneck |
/hold |
{{% notice warning %}} | ||
Kubermatic officially does not have native GitOps support yet. This article explains how you can kickstart that journey with ArgoCD right now. **Please use this setup in production at your own risk.** | ||
{{% /notice %}} |
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 should be an Alpha version as a standard way for KKP
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.
Text updated. please review
## Need of GitOps solution | ||
Kubermatic Kubernetes Platform is very versatile solution to create and manage Kubernetes clusters (user-clusters) across plethora of Cloud providers and on-prem virtualizaton platforms. But this flexibility also means that there are good amount of moving parts. Kubermatic Kubernetes Platform (KKP) provides various tools to manage user-clusters across various regions and cloud. | ||
|
||
This is why, if we utilize a GitOps solution to manage KKP and it's upgrades, KKP administrator would have better peace of mind. While KKP installation does not come ready with a GitOps solution, we have provided [an unofficial component for ArgoCD](https://github.com/kubermatic/community-components/tree/master/ArgoCD-managed-seed) based KKP management. |
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.
The code should be moved in the https://github.com/kubermatic/kubermatic repo
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.
PR raised - kubermatic/kubermatic#13705
## Further improvements which still to be done | ||
1. Use Secrets folder (e.g. with git-crypt) | ||
1. Sync Presets | ||
1. Thanos Application | ||
1. Can we look at moving Argo App templates to ApplicationSet / App of Apps? | ||
1. Optional External-DNS app so that DNS entries can be done separately. | ||
1. Can we run make targets via Github actions? |
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 track this a dedicated issues instead mention it in the docs
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.
Removed the issues from here. I have the copy with me. I will address them in future.
@scheeles - I have addressed your review comments. Please check once more. |
/approve |
LGTM label has been added. Git tree hash: 5802a21870f1512fd56b4b370893e3c03acdf0c5
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xrstf The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Step by step tutorial to explain how to use ArgoCD for Gitops based management of KKP master and seed.