Coordinate with kubernetes-sigs/secrets-store-csi-driver to support openbao as an accepted provider

[jessebot]

We need to submit a PR to https://github.com/kubernetes-sigs/secrets-store-csi-driver to add openbao as a valid provider, as right now, our SecretProviderClass resources all have to use provider: vault because otherwise, they all fail, as only a few providers are recognized and tested:

• https://github.com/kubernetes-sigs/secrets-store-csi-driver?tab=readme-ov-file#test-status
• https://secrets-store-csi-driver.sigs.k8s.io/getting-started/usage#create-your-own-secretproviderclass-object

Per their docs:

apiVersion: secrets-store.csi.x-k8s.io/v1
kind: SecretProviderClass
metadata:
  name: my-provider
spec:
  provider: vault        # accepted provider options: akeyless or azure or vault or gcp
  parameters:            # provider-specific parameters

Originally posted by @jessebot in #4 (comment)

[jessebot]

I've submitted kubernetes-sigs/secrets-store-csi-driver#1580 to get this ball rolling :)

[glad2os]

Based on the documentation the provider is openbao

Thanks for the clarification about the proper provider - vault. Subscribing for this topic and waiting for patches ahead)

My case is

  Warning  FailedMount  4s (x5 over 12s)  kubelet            MountVolume.SetUp failed for volume "openbao-db-creds" : rpc error: code = Unknown desc = failed to mount secrets store objects for pod tg-bot/tg-bot-6dc869b644-wd8cz, err: error connecting to provider "openbao": provider not found: provider "openbao"