vault-secrets-operator
cluster-api
Our great sponsors
vault-secrets-operator | cluster-api | |
---|---|---|
5 | 43 | |
609 | 3,342 | |
- | 2.5% | |
7.9 | 9.9 | |
7 days ago | 6 days ago | |
Go | Go | |
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.
vault-secrets-operator
- Toyota Accidently Exposed A Secret Key Publicly On GitHub For Five Years
-
Learning with K3s at home. Is it "better" to store secrets encrypted in the git repo (e.g., sealed-secrets) or in a separately managed secret database (e.g., vault)?
For home use, I wouldn't bother with Vault unless that's really what you want to learn. Then it's worth looking into setting something up where you could use vault secrets, using one of the available options (I haven't seen the vault-secrets-operator being mentioned).
-
Hashicorp Vault integration with Secret objects
It is but it affects vault-secrets-operator too, see https://github.com/ricoberger/vault-secrets-operator/issues/104 (and no, I’ve only use vault-secrets-operator)
-
Automation assistants: GitOps tools in comparison
If you are using an external KMS in any case, then there are other options, such as the kubernetes-external-secrets operator that was originally started by GoDaddy and the externalsecret-operator from Container Solutions. If you use HashiCorp Vault, you also have the option of using the Vault Secrets operator. This works similarly to the Sealed Secrets Operator, but instead of managing its own key material, it retrieves the secrets from Vault. The CNCF Technology Radar from January 2021 provides an overview of the types of tools that are available for secrets management.
cluster-api
-
5-Step Approach: Projectsveltos for Kubernetes add-on deployment and management on RKE2
In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.
-
“Ansible for DevOps” eBook by Jeff Geerling Is Now Free
4. Having moved to a container orchestrator, all of my nodes are immutable. Hardware and VM instances _can_ be born magically into existence. Nearly all infra providers support [cluster-api](https://cluster-api.sigs.k8s.io/). Network infrastructure can now be managed with TF, so I go that route.
- PR to docs are welcome.
-
Cluster API Theoretical and Hands-On Breakdown
## Linux curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.4.4/clusterctl-linux-amd64 -o clusterctl sudo install -o root -g root -m 0755 clusterctl /usr/local/bin/clusterctl ## Mac brew install clusterctl
-
Thank you and good bye
Did you ever try CAPI? https://github.com/kubernetes-sigs/cluster-api
-
Is it possible to install Rancher to manage an already functioning K8S?
You might find interesting the capi-rancher-import k8s operator we use in Sylva, it would adopt in Rancher server the Cluster API created k8s clusters (with bootstrap provider kubeadm or even rke2 - you can lookup CAPBR for the latter). I understand your clusters are not created by Cluster API, so if you could move the workloads/resources to new clusters created by Cluster API, this can come handy. (Adoption of non-CAPI clusters into CAPI is not yet a standard practice, more in https://github.com/kubernetes-sigs/cluster-api/issues/7776)
-
What tool suggestions do you have for someone who's gonna set up an on-premise k8 cluster? Which tools do you use?
Most of the comments have mentioned older tools like kubespray, Ansible, Rancher etc. I would suggest the cloud native way using ClusterAPI or use a tool that relies on ClusterAPI in the backend called Talos
-
Multi-tenancy in Kubernetes
Cluster API
-
Scaling Event-Driven Applications Made Easy with Sveltos Cross-Cluster Configuration
Sveltos is a powerful open source project that makes managing Kubernetes add-ons a breeze. It automatically discovers ClusterAPI powered clusters and allows you to easily register any other cluster (like GKE). Then, it seamlessly manages Kubernetes add-ons across all your clusters.
- Schulungen für den Berufseinstieg nach dem Bachelor
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
rancher - Complete container management platform
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
kops - Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
sops - Simple and flexible tool for managing secrets
karmada - Open, Multi-Cloud, Multi-Cluster Kubernetes Orchestration
argocd-vault-plugin - An Argo CD plugin to retrieve secrets from Secret Management tools and inject them into Kubernetes secrets
terraform-k8s - Terraform Cloud Operator for Kubernetes
Flux - Successor: https://github.com/fluxcd/flux2
kcp - Kubernetes-like control planes for form-factors and use-cases beyond Kubernetes and container workloads.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
eksctl - The official CLI for Amazon EKS