docs/vault-secrets-operator v0.3.4 release update (#23775)

website/content/docs/platform/k8s/vso/api-reference.mdx

@@ -7,7 +7,7 @@ description: >-
 
 <!--
   copied from docs/api/api-reference.md in the vault-secrets-operator repo.
-  commit SHA=787fa70aa4ef1b8c118e15991bd3b712eed4479c
+  commit SHA=7efe3dd7b7558369b736a5cfd174dd16bd0b8776
 -->
 # API Reference
 

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

@@ -11,7 +11,7 @@ The chart is customizable using
 [Helm configuration values](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing).
 
 <!-- DO NOT EDIT. The docs below are generated automatically. To change, edit
-                  the vault-secrets-operator repo's values.yaml: file commit=e9c2b499105d977fa23a9f746186253991ebcee1 -->
+                  the vault-secrets-operator repo's values.yaml: file commit=d2307002434ffd899f7982f9827f427dbb6295e6 -->
 <!-- codegen: start -->
 
 ## Top-Level Stanzas
@@ -119,7 +119,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.3.3`)
+      - `tag` ((#v-controller-manager-image-tag)) (`string: 0.3.4`)
 
     - `clientCache` ((#v-controller-manager-clientcache)) - Configures the client cache which is used by the controller to cache (and potentially persist) vault tokens that
       are the result of using the VaultAuthMethod. This enables re-use of Vault Tokens
@@ -275,12 +275,12 @@ Use these links to navigate to a particular top-level stanza.
 
         - `memory` ((#v-controller-manager-resources-requests-memory)) (`string: 64Mi`)
 
-  - `podSecurityContext` ((#v-controller-podsecuritycontext)) - Configures the Pod security context
+  - `podSecurityContext` ((#v-controller-podsecuritycontext)) - Configures the Pod Security Context
     https://kubernetes.io/docs/tasks/configure-pod-container/security-context
 
     - `runAsNonRoot` ((#v-controller-podsecuritycontext-runasnonroot)) (`boolean: true`)
 
-  - `securityContext` ((#v-controller-securitycontext)) - Configures the container security context
+  - `securityContext` ((#v-controller-securitycontext)) - Configures the Container Security Context
     https://kubernetes.io/docs/tasks/configure-pod-container/security-context
 
     - `allowPrivilegeEscalation` ((#v-controller-securitycontext-allowprivilegeescalation)) (`boolean: false`)

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

@@ -30,13 +30,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.3.3       	0.3.3     	Official HashiCorp Vault Secrets Operator Chart
+hashicorp/vault-secrets-operator	0.3.4       	0.3.4     	Official HashiCorp Vault Secrets Operator Chart
 ```
 
 Then install the Operator:
 
 ```shell-session
-$ helm install --version 0.3.3 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
+$ helm install --version 0.3.4 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
 ```
 
 
@@ -65,10 +65,10 @@ $ helm show crds --version <TARGET_VSO_VERSION> hashicorp/vault-secrets-operator
 $ helm upgrade --version <TARGET_VSO_VERSION> --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
 ```
 
-For example, if you are upgrading to VSO 0.3.3:
+For example, if you are upgrading to VSO 0.3.4:
 ```shell-session
-$ helm show crds --version 0.3.3 hashicorp/vault-secrets-operator | kubectl apply -f -
+$ helm show crds --version 0.3.4 hashicorp/vault-secrets-operator | kubectl apply -f -
-$ helm upgrade --version 0.3.3 --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
+$ helm upgrade --version 0.3.4 --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
 ```
 
 ## Updating CRDs
@@ -83,9 +83,9 @@ To update the VSO CRDs, replace `<TARGET_VSO_VERSION>` with the VSO version you
 $ helm show crds --version <TARGET_VSO_VERSION> hashicorp/vault-secrets-operator | kubectl apply -f -
 ```
 
-For example, if you are upgrading to VSO 0.3.3:
+For example, if you are upgrading to VSO 0.3.4:
 ```shell-session
-$ helm show crds --version 0.3.3 hashicorp/vault-secrets-operator | kubectl apply -f -
+$ helm show crds --version 0.3.4 hashicorp/vault-secrets-operator | kubectl apply -f -
 
 customresourcedefinition.apiextensions.k8s.io/hcpauths.secrets.hashicorp.com created
 customresourcedefinition.apiextensions.k8s.io/hcpvaultsecretsapps.secrets.hashicorp.com created

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

@@ -23,7 +23,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.3.3 \
+  --version 0.3.4 \
   --values values.yaml
 ```
 
@@ -56,7 +56,7 @@ controller:
   manager:
     image:
       repository: registry.connect.redhat.com/hashicorp/vault-secrets-operator
-      tag: 0.3.3-ubi
+      tag: 0.3.4-ubi
     resources:
       limits:
         memory: 256Mi