openbao-k8s and CSI driver unfinished

[rndmh3ro]

I wanted to us ethe openbao-agent-injector and noticed that there is no documentation about these on the website, because they're in draft and unfinished: #969

Is this still the case? Is there an ETA for it?

[satoqz]

AFAIK @pree is working on these but there is no release yet, so tagging here.

[pree]

csi driver is ready to be used and should also be part of the documentation. There are also multiple releases already :)

On the agent injector I'm working on and is closed to being released, docs following soon after

[wondering639]

csi driver is ready to be used and should also be part of the documentation. There are also multiple releases already :)

On the agent injector I'm working on and is closed to being released, docs following soon after

The docs that were mentioned to be released, are these https://openbao.org/docs/platform/k8s/helm/ and https://openbao.org/docs/platform/k8s/csi/ ? Both mention the latest supported Kubernetes version is 1.33, which is end of life in a few days, see https://kubernetes.io/releases/ Is the information that the latest supported Kubernetes version is 1.33 correct or maybe outdated? Also for new deployments, is the csi driver or the agent approach the recommended solution? Is that something that could maybe be added to the docs? :-) Thanks!

[pree]

Good catch, the 1.33 is outdated. It's working fine against 1.36 in my tests. I'll update the documentation.

Whether to go for External Secrets Operator, CSI or Agent Injector really depends on your use-case. We do support all three methods as they are inherently different. For stateful workloads I would go the agent injector route, otherwise either CSI or ESO. CSI does have increased complexity, so if your app cannot read secrets from the filesystem and you just need k8s secrets to be injected as env variables I would definitely go the ESO route.