proxmox-csi-plugin
secrets-store-csi-driver-provider-azure
| proxmox-csi-plugin | secrets-store-csi-driver-provider-azure | |
|---|---|---|
| 1 | 5 | |
| 192 | 427 | |
| - | 1.2% | |
| 8.3 | 7.4 | |
| 8 days ago | 7 days ago | |
| Go | Go | |
| 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.
proxmox-csi-plugin
-
Proxmox CSI for Kubernetes
I think quite a few people here might be running some sort of Kubernetes flavor on Proxmox. In that case, you might want to have a look at https://github.com/sergelogvinov/proxmox-csi-plugin. It's a CSI Controller for Proxmox! It simply creates Proxmox volumes (ZFS, LVM, whatever your setup provides) and natively attaches them to your VMs, so Kubernetes can mount them into your containers. No fiddling around with Ceph, NFS and such needed :)
secrets-store-csi-driver-provider-azure
- One main source of vulnerabilities in DevOps pipelines is how secrets like keys, certificates, and credentials are managed. Many product engineering teams, for the sake of expediency, hard-code their secrets. This is extremely dangerous.
-
Shhhh... Kubernetes Secrets Are Not Really Secret!
The driver can also sync changes to secrets. The driver currently supports Vault, AWS, Azure, and GCP providers. Secrets Store CSI Driver can also sync provider secrets as Kubernetes secrets; if required, this behavior needs to be explicitly enabled during installation.
-
A better way to manage secrets: reference an external secret defined in the cloud provider environment (please support the idea or give your feedback)
Azure SS-CSI driver
-
Kubernetes with Asp.NET and React and Azure DevOps
Azure Key Vault Provider for Secrets Store CSI Driver allows you to get secret contents stored in an Azure Key Vault instance and use the Secrets Store CSI driver interface to mount them into Kubernetes pods.
-
Service for storing API keys and Kubernetes secrets
Key vault is a good Azure native option. Take look at the secret store CSI driver for Azure https://github.com/Azure/secrets-store-csi-driver-provider-azure
What are some alternatives?
lvm-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend LVM2 data storage stack.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
directpv - Simple Kubernetes CSI driver for Direct Attached Storage :minidisc:
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
csi-driver-nfs - This driver allows Kubernetes to access NFS server on Linux node.
ingress-nginx - Ingress-NGINX Controller for Kubernetes
container-image-csi-driver - Kubernetes CSI driver for mounting image
truenas-csp - TrueNAS Container Storage Provider for HPE CSI Driver for Kubernetes
hwameistor - Hwameistor is an HA local storage system for cloud-native stateful workloads.
secrets-store-csi-driver - Secrets Store CSI driver for Kubernetes secrets - Integrates secrets stores with Kubernetes via a CSI volume.
kadalu - A lightweight Persistent storage solution for Kubernetes / OpenShift / Nomad using GlusterFS in background. More information at https://kadalu.tech
explore - Community-curated topic and collection pages on GitHub