flagger
kubernetes-external-secrets
Our great sponsors
flagger | kubernetes-external-secrets | |
---|---|---|
14 | 26 | |
4,725 | 2,584 | |
2.0% | - | |
8.7 | 7.7 | |
10 days ago | almost 2 years ago | |
Go | JavaScript | |
Apache License 2.0 | MIT License |
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.
flagger
- A K8s progressive delivery tool
-
Progressive Delivery on AKS: A Step-by-Step Guide using Flagger with Istio and FluxCD
Flagger
-
API release strategies with API Gateway
Where appropriate, canary releases are an excellent option, as the percentage of traffic exposed to the canary is highly controlled. The trade-off is that the system must have good monitoring in place to be able to quickly identify an issue and roll back if necessary (which can be automated). This guide shows you how to use Apache APISIX and Flagger to quickly implement a canary release solution.
-
GitOps using Flux and Flagger
What is Flagger? Flagger is a Progressive Delivery tool that automates the release process for applications running on Kubernetes. Under the hood, both tools are built on top of a modular GitOps toolkit. It is the main reason why Flagger compliments Flux.
- RollingUpdate but with testing the new pods first for a few minutes
-
Interesting tools?
flagger: Automated canary using istio/linkerd
-
How to rebalance underutilized nodes with CA without single replica Pod downtime?
I would suggest trying a-b deployment in this case using flagger. It will spin up a new instance and gradually rotate out old ones. Maybe that can be helpful in this weird situation :)
-
argo-rollouts VS flagger - a user suggested alternative
2 projects | 25 Jan 2022
ArgoRollouts offers Canary and BlueGreen deployment strategies for Kubernetes Pods. It's a drop-in replacement for the v1.Deployment object. Flagger is similar what it offers, extending Kubernetes to support Canary and BlueGreen deployment strategies.
-
How do you implement blue/green deployments ?
Check https://argoproj.github.io/argo-rollouts/ and https://flagger.app/
- ISO kubernetes tool or operator that automatically rolls over to a backup repo on failures
kubernetes-external-secrets
- aws secrets with eks ,Teffarorm & helm
-
Securing Kubernetes Secrets with HashiCorp Vault
$ helm repo add external-secrets https://external-secrets.github.io/kubernetes-external-secrets/ "external-secrets" has been added to your repositories $ helm install k8s-external-secrets external-secrets/kubernetes-external-secrets -f values.yaml NAME: k8s-external-secrets LAST DEPLOYED: Wed Mar 23 22:50:35 2022 NAMESPACE: default STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: The kubernetes external secrets has been installed. Check its status by running: $ kubectl --namespace default get pods -l "app.kubernetes.io/name=kubernetes-external-secrets,app.kubernetes.io/instance=k8s-external-secrets" Visit https://github.com/external-secrets/kubernetes-external-secrets for instructions on how to use kubernetes external secrets
-
SimpleSecrets: A self-hosted K8S Secrets Manager Operator
I’m reading above that you weren’t aware of sealed-secrets. So I guess that you are not familiar with ExternalSecrets secrets neither. Very solid project
- Managing json config files for apps deployed to k8s at scale
-
1Password Has Raised $620M
They probably should merge with https://github.com/external-secrets/kubernetes-external-secr...
- Recommended way of securing AWS secret key and id in K8s secrets for pulling images from AWS ECR
-
Do you have a TODO checklist when creating clusters from scratch?
I do not recommend vault if you are not experienced. It is a heavy infra to manage. I suggest looking into https://github.com/external-secrets/kubernetes-external-secrets and selecting the tool offered by your cloud providers.
-
Secrets usage
This is where things like the vault agent sidecar or projects like external secrets come in and allow you to inject / sync your secrets backend and your Kubernetes workloads :)
-
Cloud password managements
Depending on what platform you are on, you could use the AWS SDK or a tool like external-secrets (for Kubernetes).
-
Kuberentes CI/CD
We don't keep anything sensitive inside of Helm charts. We use AWS Secrets Manager and external-secrets
What are some alternatives?
argo-rollouts - Progressive Delivery for Kubernetes
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
argo-cd - Declarative Continuous Deployment for Kubernetes
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
spinnaker - Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
Flux - Successor: https://github.com/fluxcd/flux2
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
terraform-k8s - Terraform Cloud Operator for Kubernetes
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
terraform-controller - Use K8s to Run Terraform
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!