ahn heesuk
06/06/2022, 7:51 AMGitOps
+ ArgoCD
to deploy to a Kubernetes cluster after commits and merges in Git.
This works fine, but we want to take the user experience to the next level beyond committing to Git every time.
Using the Internal Developer Portal, users want to be able to skaffolding and management of the application they want with a click.
But the difficulty I feel here is the Git Layer.
Since GitOps is distributed using the Git Repository, all changes must occur in the Git Repo. (Single Source of Truth)
If you change the value (eg. replicas, helm value...) on the dashboard, you also need to commit it to Git. What is the best practice in this case?
1. When a change value is triggered in the dashboard, the operator or API server commits it to Git on its behalf.
2. You cannot modify the dashboard after scaffolding, only the Read Only mode is allowed.
If you want to change the value, you have to edit it directly in Git.
Anyone running GitOps and dashboards together? I'm curious about your experience. 🤔Mitesh Sharma
06/06/2022, 3:04 PMahn heesuk
06/07/2022, 1:25 PMMitesh Sharma
06/07/2022, 2:32 PMLaszlo Fogas
08/24/2022, 11:39 AM