flux2-kustomize-helm-example
k8s-wait-for
Our great sponsors
flux2-kustomize-helm-example | k8s-wait-for | |
---|---|---|
9 | 6 | |
847 | 556 | |
4.7% | - | |
4.3 | 0.0 | |
about 1 month ago | 14 days ago | |
Shell | Shell | |
Apache License 2.0 | MIT License |
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
- 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?
-
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.
-
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
k8s-wait-for
-
Managing external database versions in Kubernetes
You would then use an init-container like k8s-wait-for to only launch the new version of the app once the database has been updated.
-
k8s-wait-for VS docker-k8s-wait-for-it - a user suggested alternative
2 projects | 4 Nov 2021
- Setting up an order in which containers would start
What are some alternatives?
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
docker-k8s-wait-for-it - Init container for Kubernetes to ensure a service, pods, or DNS are correctly configured before allowing the other containers in the pod to start.
k8s-gitops - GitOps principles to define kubernetes cluster state via code
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]
release-please-action - automated releases based on conventional commits
argo - Workflow Engine for Kubernetes
gitops-playground - Creates a complete GitOps-based operational stack on your Kubernetes clusters
PIVT - Helm charts for running and operating Hyperledger Fabric in Kubernetes. Previously hosted at https://github.com/APGGroeiFabriek/PIVT.
reliza-cli - CLI to interact with Reliza Hub
k8s-gitops - Specify my Kubernetes cluster declaratively
helm-secrets - DEPRECATED A helm plugin that help manage secrets with Git workflow and store them anywhere [Moved to: https://github.com/zendesk/helm-secrets]