renovate-helm-releases
flux2-kustomize-helm-example
renovate-helm-releases | flux2-kustomize-helm-example | |
---|---|---|
1 | 9 | |
29 | 887 | |
- | 4.3% | |
6.8 | 3.8 | |
about 2 years ago | 21 days ago | |
Python | Shell | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
renovate-helm-releases
flux2-kustomize-helm-example
- Flux: can I add a monitored path after bootstrap?
- Is it possible to deploy to KIND cluster via GitHub actions?
-
How to structure Terraform with multi-env + multi-regions for TBD in monorepo
Any public repo show-casing a nice structure? (I am used to the Gitops world on K8s, and for the case of FluxCD for instance I would recommend this repo as a good practice to start multi-tenancy. https://github.com/fluxcd/flux2-kustomize-helm-example. I am looking for a similar "boilerplate" but for TF 😅)
- Am I wrong for avoiding helm completely?
- fluxcd/flux2-kustomize-helm-example: A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
-
Helm chart release management between environments
My recommendation would be to take a look at their documented example of this exact scenario with various overlays for production and staging, but you could ofc add as many as you wanted. All you would do is for production point flux to the production overlay/ directory, which then calls all your normal files but overrides some values you desire. Further to this you can keep your helm chart focused on lets say the "most-common" use case, then just call it with whatever additional values you would like, E.G here in the same repo as above. Notice the values at the bottom of the yaml file which override the charts default values.
-
Multi clusters deploy/automation
Here's an example using flux v2 to deploy to multiple environments/clusters: https://github.com/fluxcd/flux2-kustomize-helm-example
-
How do you manage multiple environments with GitOps?
We are using flux2, which uses Kustomize under the hood. It takes a little bit of time to learn about the different CRD's which are available but once you do it works excellent. They also have an example project which sounds like it might fit your use case https://github.com/fluxcd/flux2-kustomize-helm-example
-
Version Control / Tracked Changes For K8
As /u/vincentdesmet mentioned Kustomize will most likely to solve your many "apps" with slightly difference issue, this is a good example https://github.com/fluxcd/flux2-kustomize-helm-example (also include helm one)
What are some alternatives?
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
home-ops - Wife approved HomeOps driven by Kubernetes and GitOps using Flux
k8s-gitops - GitOps principles to define kubernetes cluster state via code
k8s-platform-lcm - A faster and easier way to manage the lifecycle of applications and tools, running and living around your Kubernetes platform
release-please-action - automated releases based on conventional commits
up-to-date-react-template - â™» An Always up-to-date React template with Typescript, Jest, Prettier, Github Actions and Renovate
gitops-playground - Creates a complete GitOps-based operational stack on your Kubernetes clusters
k8s-wait-for - A simple script that allows to wait for a k8s service, job or pods to enter a desired state
reliza-cli - CLI to interact with Reliza Hub