flux2-kustomize-helm-example
terraform-best-practices
flux2-kustomize-helm-example | terraform-best-practices | |
---|---|---|
9 | 2 | |
887 | 1,707 | |
4.3% | - | |
3.8 | 5.8 | |
19 days ago | 6 months ago | |
Shell | HCL | |
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.
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)
terraform-best-practices
What are some alternatives?
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
fortinet-azure-solutions - A set of Azure Templates for getting you started in Azure with Fortinet solutions. This repository is a place for beta releases and work on the latest templates to be published on github.com/fortinet or custom templates.
k8s-gitops - GitOps principles to define kubernetes cluster state via code
atlantis - Terraform Pull Request Automation
release-please-action - automated releases based on conventional commits
terraform-github-action-cache-example - Caching Terraform providers within a GitHub Actions Workflow run to improve execution times.
gitops-playground - Creates a complete GitOps-based operational stack on your Kubernetes clusters
personal-zero-trust-hashicorp-vault - Cloudflare for Teams + HashiCorp Vault = Zero Trust Love
k8s-wait-for - A simple script that allows to wait for a k8s service, job or pods to enter a desired state
sops - Simple and flexible tool for managing secrets
reliza-cli - CLI to interact with Reliza Hub
terraform-aws-datadog-metric-stream - Boilerplate Terraform configuration for AWS infrastructure to support CloudWatch Metric Streams for delivery of metrics into Datadog.