bank-vaults
logging-operator
Our great sponsors
bank-vaults | logging-operator | |
---|---|---|
10 | 7 | |
0 | 1,484 | |
- | 1.6% | |
0.0 | 9.7 | |
7 months ago | 4 days ago | |
Go | Go | |
Apache License 2.0 | 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.
bank-vaults
-
Self-hosted Secrets Manager (or something alike)
there's https://github.com/banzaicloud/bank-vaults wich is a wrapper for hashivault, so not exactly what you're looking for but worth looking into.
-
Secrets Management on Kubernetes: How do you handle it?
https://github.com/banzaicloud/bank-vaults. Mind you after Cisco bought Banzai work on this project seems to have stopped. It works very well for us though.
-
Secrets Management with Hashicorp Vault - which integration point to use? Sidecar Injector? ESO?
We are using Banzai Bank Vaults Webhook and we’re very happy with it.
-
Project: Running a local cluster with TLS, ArgoCD GitOps, Vault and a PostgreSQL operator
If you ever want to see vault at that kind of level check out bank-vaults. Overkill for many, but it sounds like a decent fit for what you've already got in place and might reduce the boilerplate.
-
Run a pod in a namespace without having access to it's secrets?
Use vault-env (we use https://github.com/banzaicloud/bank-vaults) to inject the secret as an ENV var to the pod at runtime, based on Vault's Kubernetes auth
-
Secrets storage best practices
We use bank vault to inject secrets as environment variables. This does not require changes to the app. A sidecar is automatically added to the pod to retrieve the secrets and inject them in the app runtime. Here’s the link https://github.com/banzaicloud/bank-vaults
- How to manage passwords in Helm
- Homelab: Cluster Architecture
-
Kubernetes authentication from multiple, external clusters
I can follow up with examples if you'd like. You might like BanzaiCloud's Bank Vaults. We personally only use the Configurer component which just provides useful mechanisms to dynamically, or once off, configure Vault via data structures we supplied via ConfigMap.
-
Secrets Managers for Kubernetes (Vault (Hashi), Conjur (CyberArk), Platform Specific, etc)
Encrypted secrets can't be more than a temporary solution. That's why I'm not a fan of SOPS/Sealed Secrets/etc. I think the future for both security and usability is dynamic injection. Vault is the dopeness but I'm not a fan of the upstream Vault Injector -- shared volumes are a step backwards. It's all about the BanzaiCloud Vault Webhook -- secrets **only ever available to the running process**, rotation means: update the value in vault and bounce the pod, done. This is the way.
logging-operator
-
Multi-tenant logging on Kubernetes
Learn about how the Logging operator (CNCF Sandbox project) enables multi-tenant scenarios:
-
Banzai Logging Helm Chart
Banzai moved it out into a dedicated kube-logging organization on Github, at https://github.com/kube-logging/logging-operator 4.0 released a few weeks ago.
- Logging sidecar for cronjobs: how to have them complete the run?
-
CrashLoopBackOff - how to get logs from the first pod that failed and is over 15 days old?
Shameless plug, I recommend you give a shot to https://github.com/banzaicloud/logging-operator - I am one of the maintainers.
-
Homelab: Cluster Architecture
Logging Operator Helm Chart - https://github.com/banzaicloud/logging-operator
-
Which stacks are complex to install on Kubernetes?
There is even whole projects setup to solve the horrible nature that is efk / elk. See https://github.com/banzaicloud/logging-operator
-
Logging Operator to setup logging in Kubernetes cluster
How does this compare to/differ from the Banzai Logging operator?
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
helm-charts
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
data-center-helm-charts - Helm charts for Atlassian's Data Center products
vault-csi-provider - HashiCorp Vault Provider for Secret Store CSI Driver
k3s-home-cluster - Sets up a Kubernetes cluster using Ansible
secrets-store-csi-driver-provider-azure - Azure Key Vault provider for Secret Store CSI driver allows you to get secret contents stored in Azure Key Vault instance and use the Secret Store CSI driver interface to mount them into Kubernetes pods.
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
k3s - Lightweight Kubernetes
helm-charts - A curated set of Helm charts brought to you by codecentric
faas-netes - Serverless Functions For Kubernetes