[docs] Update docs for VSO release 0.4.3 (#24792)

* Update docs for VSO release 0.4.3
This commit is contained in:
Kyle Schochenmaier
2024-01-10 20:12:09 -06:00
committed by GitHub
parent 3fc6115c87
commit aed43fe80e
3 changed files with 11 additions and 11 deletions

View File

@@ -11,7 +11,7 @@ The chart is customizable using
[Helm configuration values](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing). [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 <!-- DO NOT EDIT. The docs below are generated automatically. To change, edit
the vault-secrets-operator repo's values.yaml: file commit=d2307002434ffd899f7982f9827f427dbb6295e6 --> the vault-secrets-operator repo's values.yaml: file commit=dbdfa37e122bd91a4db0bb016970b717aca544f5 -->
<!-- codegen: start --> <!-- codegen: start -->
## Top-Level Stanzas ## 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`) - `repository` ((#v-controller-manager-image-repository)) (`string: hashicorp/vault-secrets-operator`)
- `tag` ((#v-controller-manager-image-tag)) (`string: 0.4.2`) - `tag` ((#v-controller-manager-image-tag)) (`string: 0.4.3`)
- `clientCache` ((#v-controller-manager-clientcache)) - Configures the client cache which is used by the controller to cache (and potentially persist) vault tokens that - `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 are the result of using the VaultAuthMethod. This enables re-use of Vault Tokens

View File

@@ -30,13 +30,13 @@ $ helm repo add hashicorp https://helm.releases.hashicorp.com
```shell-session ```shell-session
$ helm search repo hashicorp/vault-secrets-operator $ helm search repo hashicorp/vault-secrets-operator
NAME CHART VERSION APP VERSION DESCRIPTION NAME CHART VERSION APP VERSION DESCRIPTION
hashicorp/vault-secrets-operator 0.4.2 0.4.2 Official HashiCorp Vault Secrets Operator Chart hashicorp/vault-secrets-operator 0.4.3 0.4.3 Official HashiCorp Vault Secrets Operator Chart
``` ```
Then install the Operator: Then install the Operator:
```shell-session ```shell-session
$ helm install --version 0.4.2 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator $ helm install --version 0.4.3 --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 $ 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.4.2: For example, if you are upgrading to VSO 0.4.3:
```shell-session ```shell-session
$ helm show crds --version 0.4.2 hashicorp/vault-secrets-operator | kubectl apply -f - $ helm show crds --version 0.4.3 hashicorp/vault-secrets-operator | kubectl apply -f -
$ helm upgrade --version 0.4.2 --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator $ helm upgrade --version 0.4.3 --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator
``` ```
## Updating CRDs ## 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 - $ helm show crds --version <TARGET_VSO_VERSION> hashicorp/vault-secrets-operator | kubectl apply -f -
``` ```
For example, if you are upgrading to VSO 0.4.2: For example, if you are upgrading to VSO 0.4.3:
```shell-session ```shell-session
$ helm show crds --version 0.4.2 hashicorp/vault-secrets-operator | kubectl apply -f - $ helm show crds --version 0.4.3 hashicorp/vault-secrets-operator | kubectl apply -f -
customresourcedefinition.apiextensions.k8s.io/hcpauths.secrets.hashicorp.com created customresourcedefinition.apiextensions.k8s.io/hcpauths.secrets.hashicorp.com created
customresourcedefinition.apiextensions.k8s.io/hcpvaultsecretsapps.secrets.hashicorp.com created customresourcedefinition.apiextensions.k8s.io/hcpvaultsecretsapps.secrets.hashicorp.com created

View File

@@ -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 \ $ helm install vault-secrets-operator hashicorp/vault-secrets-operator \
--create-namespace \ --create-namespace \
--namespace vault-secrets-operator \ --namespace vault-secrets-operator \
--version 0.4.2 \ --version 0.4.3 \
--values values.yaml --values values.yaml
``` ```
@@ -56,7 +56,7 @@ controller:
manager: manager:
image: image:
repository: registry.connect.redhat.com/hashicorp/vault-secrets-operator repository: registry.connect.redhat.com/hashicorp/vault-secrets-operator
tag: 0.4.2-ubi tag: 0.4.3-ubi
resources: resources:
limits: limits:
memory: 256Mi memory: 256Mi