scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-10-30 18:17:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

backport of commit 9e063f31d7 (#24370)

Browse Source 
Co-authored-by: Ben Ash <32777270+benashz@users.noreply.github.com>
This commit is contained in:
hc-github-team-secure-vault-core
2023-12-04 20:33:07 -05:00
committed by GitHub
parent 1e612090a3
commit c5c7c98693
3 changed files with 11 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
website/content/docs/platform/k8s/vso/helm.mdx
View File

@@ -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.0`) - `tag` ((#v-controller-manager-image-tag)) (`string: 0.4.1`)
- `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
@@ -262,8 +262,7 @@ Use these links to navigate to a particular top-level stanza.
headers: headers:
X-vault-something1: "foo" X-vault-something1: "foo"
- `maxConcurrentReconciles` ((#v-controller-manager-maxconcurrentreconciles)) (`integer: ""`) - Defines the maximum number of concurrent reconciles by the controller. - `maxConcurrentReconciles` ((#v-controller-manager-maxconcurrentreconciles)) (`integer: ""`) - Defines the maximum number of concurrent reconciles for each controller.
NOTE: Currently this is only used by the reconciliation logic of dynamic secrets.
default: 100 default: 100

14
website/content/docs/platform/k8s/vso/installation.mdx
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.0 0.4.0 Official HashiCorp Vault Secrets Operator Chart hashicorp/vault-secrets-operator 0.4.1 0.4.1 Official HashiCorp Vault Secrets Operator Chart
``` ```
Then install the Operator: Then install the Operator:
```shell-session ```shell-session
$ helm install --version 0.4.0 --create-namespace --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator $ helm install --version 0.4.1 --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.0: For example, if you are upgrading to VSO 0.4.1:
```shell-session ```shell-session
$ helm show crds --version 0.4.0 hashicorp/vault-secrets-operator | kubectl apply -f - $ helm show crds --version 0.4.1 hashicorp/vault-secrets-operator | kubectl apply -f -
$ helm upgrade --version 0.4.0 --namespace vault-secrets-operator vault-secrets-operator hashicorp/vault-secrets-operator $ helm upgrade --version 0.4.1 --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.0: For example, if you are upgrading to VSO 0.4.1:
```shell-session ```shell-session
$ helm show crds --version 0.4.0 hashicorp/vault-secrets-operator | kubectl apply -f - $ helm show crds --version 0.4.1 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

4
website/content/docs/platform/k8s/vso/openshift.mdx
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.0 \ --version 0.4.1 \
--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.0-ubi tag: 0.4.1-ubi
resources: resources:
limits: limits:
memory: 256Mi memory: 256Mi