flux2-multi-tenancy VS kubernetes-external-secrets

Compare flux2-multi-tenancy vs kubernetes-external-secrets and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
flux2-multi-tenancy kubernetes-external-secrets
4 26
474 2,584
2.1% -
6.0 7.7
8 days ago almost 2 years ago
Shell JavaScript
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-multi-tenancy

Posts with mentions or reviews of flux2-multi-tenancy. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-04.
  • How does GitOps (ArgoCD, Flux) deal with cloud resources?
    3 projects | /r/devops | 4 Mar 2022
    You may look at multi tenant deployment of fluxcd at https://github.com/fluxcd/flux2-multi-tenancy where you can have shared infrastructure repo to bootstrap flux with terraform (if you wish) and then a repo per team to manage k8s resources.
  • Kuberentes CI/CD
    4 projects | /r/kubernetes | 26 Oct 2021
    Bootstrap Flux v2 to the cluster via Gitlab CI then deploy everything else using their multi tenant approach - https://github.com/fluxcd/flux2-multi-tenancy
  • Flux vs ArgoCD
    2 projects | dev.to | 7 Oct 2021
    We are exploring this GitOps trend at Playtomic. We have two k8s clusters running using Flux and ArgoCD. We have a multi-tenancy setup, that is, one repo for the cluster itself, one repo for every application we deploy in the cluster. Flux and ArgoCD image updaters are in place.
  • How do you manage multiple environments with GitOps?
    3 projects | /r/devops | 17 Apr 2021
    Maybe this is helpful https://github.com/fluxcd/flux2-multi-tenancy

kubernetes-external-secrets

Posts with mentions or reviews of kubernetes-external-secrets. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-13.

What are some alternatives?

When comparing flux2-multi-tenancy and kubernetes-external-secrets you can also consider the following projects:

flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.

argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets

argocd-image-updater - Automatic container image update for Argo CD

sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets

crossplane - The Cloud Native Control Plane

vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.

ko - Build and deploy Go applications

Bitwarden - The core infrastructure backend (API, database, Docker, etc).

gitops-catalog - Tools and technologies that are hosted on an OpenShift cluster

secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.

GitVersion - From git log to SemVer in no time

Reloader - A Kubernetes controller to watch changes in ConfigMap and Secrets and do rolling upgrades on Pods with their associated Deployment, StatefulSet, DaemonSet and DeploymentConfig – [✩Star] if you're using it!