search

saritasa-nest / saritasa-devops-helm-charts

Various helm charts
0 stars 0 forks source link

feat: add ability to define extraApps through gitops #43

Closed dmitry-mightydevops closed 2 years ago

dmitry-mightydevops commented 2 years ago

used it first time for nmbl extra apps https://github.com/saritasa-nest/saritasa-rocks-kubernetes-aws/pull/66 and nmbl-kubernetes-aws

MikhailKorol-saritasa commented 2 years ago

If we controlling sync workflow with tekton-apps, should we then remove extra-* apps? For example producebox: we implemented extra-dev to stay sync-db app in sync state with k8s repo. In current situation we don't need that app anymore. Also we don't need templates for that app in argocd subfolder for dev environment - we need only kustomize manifests. Also, can we use that ability to define apps based on helm charts?

dmitry-mightydevops commented 2 years ago

If we controlling sync workflow with tekton-apps, should we then remove extra-* apps? For example producebox: we implemented extra-dev to stay sync-db app in sync state with k8s repo. In current situation we don't need that app anymore. Also we don't need templates for that app in argocd subfolder for dev environment - we need only kustomize manifests. Also, can we use that ability to define apps based on helm charts?

Hi Misha - I'm not sure I understand the question, especially about the kustomize.

Producebox has no gitops for root app (extra-apps) per our call yesterday. This solution introduced that simple addon. So that extra-apps require no manual k apply but instead are referenced in the tekton-apps config.

Call me to discuss in your morning. So we're on the same page.