k8s-wait-for
terraform-provider-atlas
| k8s-wait-for | terraform-provider-atlas | |
|---|---|---|
| 6 | 1 | |
| 563 | 53 | |
| - | - | |
| 0.0 | 7.0 | |
| about 2 months ago | 18 days ago | |
| Shell | Go | |
| 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
terraform-provider-atlas
-
Managing external database versions in Kubernetes
I'd strongly advice against both flyway and liquibase in favor to Atlas with the respective TF provider.
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.
database-migration - Continuous Database Configuration with Flyway and Kubernetes
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]
Flyway - Flyway by Redgate • Database Migrations Made Easy.
argo - Workflow Engine for Kubernetes
liquibase - Main Liquibase Source
PIVT - Helm charts for running and operating Hyperledger Fabric in Kubernetes. Previously hosted at https://github.com/APGGroeiFabriek/PIVT.
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
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]
k8s-gitops - GitOps principles to define kubernetes cluster state via code