backport of commit 1b8c1dc (#29155)

Co-authored-by: Ben Ash <[email protected]>

website/content/docs/platform/k8s/vso/helm.mdx

@@ -6,7 +6,7 @@ description: >-
 ---
 <!-- DO NOT EDIT.
 Generated from chart/values.yaml in the vault-secrets-operator repo.
-commit SHA=08a6e5071ffa4faa486bd4b2c53b27585da4680c
+commit SHA=0bf284afea63a64e706717e2324a304be4d7f24b
 
 To update run 'make gen-helm-docs' from the vault-secrets-operator repo.
 -->
@@ -179,7 +179,7 @@ Use these links to navigate to a particular top-level stanza.
 
       - `repository` ((#v-controller-manager-image-repository)) (`string: hashicorp/vault-secrets-operator`)
 
-      - `tag` ((#v-controller-manager-image-tag)) (`string: 0.9.0`)
+      - `tag` ((#v-controller-manager-image-tag)) (`string: 0.9.1`)
 
     - `logging` ((#v-controller-manager-logging)) - logging
 
@@ -265,6 +265,16 @@ Use these links to navigate to a particular top-level stanza.
 
         default: 10000
 
+      - `numLocks` ((#v-controller-manager-clientcache-numlocks)) (`integer: ""`) - Defines the number of locks to use for the Vault client cache controller.
+        May also be set via the `VSO_CLIENT_CACHE_NUM_LOCKS` environment variable.
+
+        Setting this value less than 1 will cause the manager to set the number of locks equal
+        to the number of logical CPUs of the run host.
+
+        See the VSO help output for more information.
+
+        default: 100
+
       - `storageEncryption` ((#v-controller-manager-clientcache-storageencryption)) - StorageEncryption provides the necessary configuration to encrypt the client storage
         cache within Kubernetes objects using (required) Vault Transit Engine.
         This should only be configured when client cache persistence with encryption is enabled and

website/content/docs/platform/k8s/vso/installation.mdx

@@ -32,13 +32,13 @@ $ helm repo add hashicorp https://helm.releases.hashicorp.com
 ```shell-session
 $ helm search repo hashicorp/vault-secrets-operator
 NAME           	CHART VERSION	APP VERSION	DESCRIPTION
-hashicorp/vault-secrets-operator	0.9.0       	0.9.0     	Official HashiCorp Vault Secrets Operator Chart
+hashicorp/vault-secrets-operator	0.9.1       	0.9.1     	Official HashiCorp Vault Secrets Operator Chart
 ```
 
 Then install the Operator:
 
 ```shell-session
-$ helm install --version 0.9.0 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
+$ helm install --version 0.9.1 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
 ```
 
 ## Upgrading using Helm
@@ -78,9 +78,9 @@ You can install and update your installation using `kustomize` which allows you
 
 To install using Kustomize, download and untar/unzip the latest release from the [Releases Page](https://github.com/hashicorp/vault-secrets-operator/releases).
 ```shell-session
-$ wget -q https://github.com/hashicorp/vault-secrets-operator/archive/refs/tags/v0.9.0.tar.gz
-$ tar -zxf v0.9.0.tar.gz
-$ cd vault-secrets-operator-0.9.0/
+$ wget -q https://github.com/hashicorp/vault-secrets-operator/archive/refs/tags/v0.9.1.tar.gz
+$ tar -zxf v0.9.1.tar.gz
+$ cd vault-secrets-operator-0.9.1/
 ```
 
 Next install using `kustomize build`:

website/content/docs/platform/k8s/vso/openshift.mdx

@@ -32,7 +32,7 @@ The Vault Secrets Operator may also be installed in OpenShift using the Helm cha
 $ helm install vault-secrets-operator hashicorp/vault-secrets-operator \
   --create-namespace \
   --namespace vault-secrets-operator \
-  --version 0.9.0 \
+  --version 0.9.1 \
   --values values.yaml
 ```
 
@@ -65,7 +65,7 @@ controller:
   manager:
     image:
       repository: registry.connect.redhat.com/hashicorp/vault-secrets-operator
-      tag: 0.9.0-ubi
+      tag: 0.9.1-ubi
     resources:
       limits:
         memory: 256Mi