flux2-kustomize-helm-example VS k8s-wait-for

Compare flux2-kustomize-helm-example vs k8s-wait-for and see what are their differences.

flux2-kustomize-helm-example

A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm. (by fluxcd)

k8s-wait-for

A simple script that allows to wait for a k8s service, job or pods to enter a desired state (by groundnuty)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
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
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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

Posts with mentions or reviews of flux2-kustomize-helm-example. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-27.
  • Is it possible to deploy to KIND cluster via GitHub actions?
    2 projects | /r/kubernetes | 27 Feb 2023
  • How to structure Terraform with multi-env + multi-regions for TBD in monorepo
    5 projects | /r/Terraform | 14 Feb 2023
    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?
    4 projects | /r/kubernetes | 29 Oct 2022
  • Helm chart release management between environments
    2 projects | /r/kubernetes | 7 May 2021
    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?
    3 projects | /r/devops | 17 Apr 2021
    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

Posts with mentions or reviews of k8s-wait-for. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-25.

What are some alternatives?

When comparing flux2-kustomize-helm-example and k8s-wait-for you can also consider the following projects:

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]