Add Bitwarden Secrets Manager provider

[kvncrw]

Summary

This PR adds the Bitwarden Secrets Manager CSI Provider to the list of supported providers.

The provider implements the v1alpha1 gRPC provider protocol and enables Kubernetes workloads to mount secrets from Bitwarden Secrets Manager via the Secrets Store CSI Driver.

Provider details

• Repository: https://github.com/kvncrw/bitwarden-csi-provider
• Language: Rust
• Installation: Helm chart included
• Supported features: Sync as Kubernetes secret, Helm chart
• Not yet supported: Rotation, Windows

Changes in this PR

• docs/book/src/introduction.md — Added Bitwarden Provider link to the Supported Providers list
• docs/book/src/providers.md — Added Bitwarden column to the feature comparison table

Note

e2e tests for the Bitwarden provider will be added in a follow-up PR.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kvncrw
Once this PR has been reviewed and has the lgtm label, please assign ritazh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

This issue is currently awaiting triage.

If secrets-store-csi-driver contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

Hi @kvncrw. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[enj]

Neat, @aramase I think there is some e2e requirements we have for this?