k8s-wait-for
flux2-kustomize-helm-example
k8s-wait-for | flux2-kustomize-helm-example | |
---|---|---|
6 | 9 | |
563 | 887 | |
- | 4.3% | |
0.0 | 3.8 | |
about 2 months ago | 17 days ago | |
Shell | Shell | |
MIT License | 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.
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: A simple script that allows to wait for a k8s service, job or pods to enter a desired state
- How to Start a Pod after ALL others are Running ?
-
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
-
Rainbow deployments in Kubernetes - is this the best approach for zero-downtime with long running (hours) workloads?
We're using job to run commands as a prerequisite for a deployment (initContainer are not a good fit since we don't want these commands to run on each pod start up). We create a job with a different name (usually the commit hash) and have an initContainer in the deployment running this image: https://github.com/groundnuty/k8s-wait-for
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?
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.
flux2-multi-tenancy - Manage multi-tenant clusters with Flux
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]
k8s-gitops - GitOps principles to define kubernetes cluster state via code
argo - Workflow Engine for Kubernetes
release-please-action - automated releases based on conventional commits
PIVT - Helm charts for running and operating Hyperledger Fabric in Kubernetes. Previously hosted at https://github.com/APGGroeiFabriek/PIVT.
gitops-playground - Creates a complete GitOps-based operational stack on your Kubernetes clusters
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]
reliza-cli - CLI to interact with Reliza Hub