Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for non-LB'd HA clusters #164

Open
gtaylor opened this issue Jul 8, 2022 · 0 comments
Open

Support for non-LB'd HA clusters #164

gtaylor opened this issue Jul 8, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@gtaylor
Copy link

gtaylor commented Jul 8, 2022

If I am understanding correctly, the Vault CSI can only be pointed at a single vaultAddress. For example:

---
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  name: vault-db-creds
spec:
  provider: vault
  parameters:
    roleName: 'app'
    vaultAddress: 'https://vault.vault:8200'
    vaultCACertPath: '/vault/tls/ca.crt'
    objects: |
      - objectName: "dbUsername"
        secretPath: "database/creds/db-app"
        secretKey: "username"
      - objectName: "dbPassword"
        secretPath: "database/creds/db-app"
        secretKey: "password"

I've got a simple bare metal setup that does not include an LB solution. This means that the Vault CSI would cease to function if the single node that my SecretProviderClass points as goes down.

Would it be possible to add the ability to specify multiple Vault addresses?

    vaultAddresses: ['https://vault1.vault:8200', 'https://vault2.vault:8200', 'https://vault3.vault:8200']

Or something similar?

@tomhjp tomhjp added the enhancement New feature or request label Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants