k8s-wait-for
PIVT
Our great sponsors
k8s-wait-for | PIVT | |
---|---|---|
6 | 1 | |
563 | 211 | |
- | - | |
0.0 | 0.0 | |
about 1 month ago | about 1 year 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
PIVT
-
Kubernetes Operator for Hyperledger Fabric
This post introduces Kubernetes Operator for Hyperledger Fabric, which is a wrapper around PIVT Helm charts and makes running and operating Hyperledger Fabric in Kubernetes even more easier. Github
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.
bevel-operator-fabric - Hyperledger Fabric Kubernetes operator - Hyperledger Fabric operator for Kubernetes (v2.3, v2.4 and v2.5)
k3s-gitops - My home Kubernetes (k3s) cluster managed by GitOps (Flux2) [Moved to: https://github.com/onedr0p/home-cluster]
diginode-tools - DigiNode Tools - Setup, monitor and manage a DigiByte Full Node and/or DigiAssets Node on a Raspberry Pi 4 or Ubuntu/Debian system.
argo - Workflow Engine for Kubernetes
hl-fabric-operator - Kubernetes operator for Hyperledger Fabric
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
general-meeting - stock market based on hyperledger fabric
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]
blockgum - Blockgum is a Geth alternative as It supports HDWallet, which can generate billions of addresses. It uses Single Master Public and Private keys. No need to maintain Millions of Private keys. Backup once and you are good forever. Blockgum can read multiple chains ie Multichain Wallet Full Server side wallet solution. the https://blockgum.com
k8s-gitops - GitOps principles to define kubernetes cluster state via code
hlf-operator - Hyperledger Fabric Kubernetes operator - Hyperledger Fabric operator for Kubernetes (v2.2+) [Moved to: https://github.com/hyperledger-labs/hlf-operator]