Feature request: Support OpenBao as a spec.provider in secrets-store.csi.x-k8s.io/v1

[jessebot]

Describe the solution you'd like

I'd like to propose we please add support for OpenBao as a spec.provider.

Anything else you would like to add

OpenBao, a fork of Vault before the license change to BSL, is a Linux Foundation Project and is being actively maintained by a set of kind maintainers and collaborators. We recently forked the Vault CSI Provider repo and started testing it, but I ran into an issue where OpenBao is not recognized as a valid provider, and so I opened this issue to track it: openbao/openbao-csi-provider#5

We're happy to support this effort by submitting PRs to accommodate this. As I'm personally a little new to this repo, if you could point me in the right direction, I am happy to start on a draft PR :) Most everything should be the same as Vault for now, but with the name OpenBao as essentially an alias.

Let me know if you have follow up questions! Happy to help/collaborate 🙏

Environment

• Secrets Store CSI Driver version: (use the image tag):
  We're actually using the helm chart in our tests and that's using 1.3.2, which I believe also installs the same image tag according to the appVersion in Chart.yaml.

• Kubernetes version: (use kubectl version):

  Client Version: v1.30.2
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.30.2+k3s1

[aramase]

Hello 👋🏻

Thanks for reaching out and welcome to the community!

There are no changes required in the driver to support a provider. As long as the provider implements the RPC required for communication between driver-provider it should work.

In terms of getting the provider added to the supported provider list here, these are the steps you would need to follow: https://secrets-store-csi-driver.sigs.k8s.io/providers. We would be happy to work with you!

Feel free to reach out on slack if you have any questions.

[aramase]

@jessebot Any update on this? Let us know how we can help!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[aramase]

/remove-lifecycle stale