Just an unrelated thing I caught

priorityClassName, topologySpreadConstraints, and podDisruptionBudget are not part of this work, but they got auto-generated along with the rest of this because it looks like docs generation got missed last time.

Could you explain how you generated the content? If it's auto-generated somehow, EDU should be editing the content at the source instead of trying to edit the docs afterward.

The Helm docs are generated by the make gen-helm-docs command in the vault-secrets-operator repo. (Well, this particular iteration is from a private fork of that repo, but that's typically where the generation is done.)

Is the Education team typically added as a codeowner for field descriptions in the main Vault repo, like wherever the Vault CLI help text lives, for example? I would say this is similar to that -- the descriptions of each field lives with the fields themselves, but we have a helper script that gathers them up and spits it out in this format.

Personally I think it will impact velocity if we need to wait for an Education approver for any PR that updates the available fields in VSO (our API, essentially). Happy to change any descriptions of those fields that are inaccurate or unclear though, when you review the docs in this repo.

There's no need to make this a separate alert. We can fold it into the introduction

Sorry, I should have probably provided this information to you in advance, but the Vault Secrets Operator CSI Driver is actually a new, different offering from the Vault CSI Provider.

In light of that, to reduce confusion, we've decided to rename the Vault CSI Provider "Secrets Store CSI Provider for Vault".

So:

• Vault Secrets Operator CSI Driver -- the new offering that all my changes in the vso folder are related to
• Secrets Store CSI Provider for Vault -- the older offering, which is part of a non-HashiCorp solution called "Secrets Store CSI" that we essentially just built an extension for. All the changes in the csi folder are just me renaming that thing.

After reading that, do you think it makes sense to keep it as an alert (like "hey! you might want this other cool thing instead! y'know, our thing!!") rather than as part of the introduction to the Secrets Store CSI offering?

Or is this perhaps what the <Tip> thing is for?

@benashz Can you please verify that these comparisons are factually correct? Especially Vault Agent Injector and Secrets Store CSI Provider for Vault which I am less familiar with.