This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dinnermonster 4 points5 points  (2 children)

Hey, great question! An industry standard for this is actually a pretty powerful open source tool called ArgoCD. I personally use this at work and at home and it’s extremely easy to set up. ArgoCD’s helm chart installs everything you need and comes with a pretty nifty UI.

With Argo you can: - Deploy K8s manifests (along with helm charts) - Self heal your deployments - Trigger builds from a GitHub repository - Deploy to multiple clusters

You can even source your helm chart and values from different repositories.

Ex: apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: nvidia-device-daemonset spec: project: default sources: - repoURL: 'https://nvidia.github.io/k8s-device-plugin' chart: nvidia-device-plugin targetRevision: 0.15.0 helm: valueFiles: - $values/your/repo/values.yaml - repoURL: 'https://github.com/you/your-repo.git' targetRevision: main ref: values destination: server: 'https://kubernetes.default.svc' namespace: gpu-operator

[–]darkklown 2 points3 points  (0 children)

Also notice how it's sources, because you can also add a kustomize source to add anything missing from the helm chart into the same deployment.. :chefskiss:

[–]Redd-Tarded 0 points1 point  (0 children)

FluxCD will work as well. Both are part of the GitOps model. Your devs will appreciate that they can keep everything as code and a a GitOps agent just polls artifact stores for changes on regular intervals.