content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
exists. - `updateStrategyType` (`string: "OnDelete"`) - Configure the [Update Strategy Type](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies) for the StatefulSet. - `logLevel` (`string: ""`) - Configures the Vault server logging verbosity. If set this will override values define... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.05617908388376236,
0.029380496591329575,
-0.006513947620987892,
-0.03597365692257881,
-0.007031181361526251,
-0.06152059882879257,
-0.020990224555134773,
-0.03045976161956787,
0.052348870784044266,
0.04086949676275253,
0.0024424209259450436,
-0.015843961387872696,
0.0363769493997097,
0.0... | 0.059062 |
(`boolean: true`) - When HA mode is enabled and K8s service registration is being used, configure the route to point to the Vault active service. - `labels` (`dictionary: {}`) - Labels for the Route - `annotations` (`dictionary: {}`) - Annotations to add to the Route. This can either be YAML or a YAML-formatted multi-l... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
-0.016979647800326347,
0.06419364362955093,
-0.07557112723588943,
0.022296056151390076,
-0.024039829149842262,
-0.005299685522913933,
-0.011441498063504696,
-0.035969190299510956,
0.0018240668578073382,
-0.0022600009106099606,
0.020131105557084084,
0.00729886582121253,
0.03717288747429848,
... | 0.020763 |
probe times out. - `port` (`int: 8200`) - Port number on which livenessProbe will be checked if httpGet is used as the livenessProbe handler. ```yaml livenessProbe: enabled: true path: /v1/sys/health?standbyok=true initialDelaySeconds: 60 failureThreshold: 2 periodSeconds: 5 successThreshold: 1 timeoutSeconds: 3 port: ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.05114227533340454,
0.061644427478313446,
0.005441471002995968,
0.016694696620106697,
0.03149959072470665,
-0.030617695301771164,
-0.05768606811761856,
-0.039377421140670776,
0.05235075578093529,
0.05542277544736862,
-0.012787408195436,
-0.009346751496195793,
-0.057493869215250015,
-0.025... | 0.068483 |
or secret is mounted. If not specified the volume will be mounted to `/vault/userconfig/`. - `defaultMode` (`string: "420"`) - Default mode of the mounted files. ```yaml extraVolumes: - type: 'secret' name: 'vault-certs' path: '/etc/pki' ``` - `volumes` (`array: null`) - A list of volumes made available to all containe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.040120258927345276,
-0.0012995988363400102,
-0.022588076069951057,
-0.02040446549654007,
0.006842399947345257,
-0.04007073864340782,
-0.0365254208445549,
0.01252942718565464,
0.13388848304748535,
-0.02762470208108425,
0.05563182756304741,
-0.04097697511315346,
0.03199803829193115,
0.0176... | 0.044521 |
created for Vault. - `active` - Values that apply only to the vault-active service. - `enabled` (`boolean: true`) - When set to `true`, the vault-active Kubernetes service will be created for Vault, selecting pods which label themselves as the cluster leader with `vault-active: "true"`. - `annotations` (`dictionary: {}... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.0074812802486121655,
0.004640663042664528,
-0.04401076212525368,
0.014085251837968826,
0.02470378391444683,
0.047587282955646515,
0.0011674226261675358,
-0.030652089044451714,
0.0720285028219223,
0.0027276233304291964,
0.03662661090493202,
0.008265605196356773,
0.024299703538417816,
-0.0... | 0.129508 |
families that should be supported and the order in which they should be applied to ClusterIP as well. Can be IPv4 and/or IPv6. - `serviceAccount` - Values that configure the Kubernetes service account created for Vault. - `create` (`boolean: true`): If set to true, creates a service account used by Vault. - `name` (`st... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
-0.034634996205568314,
-0.03411049768328667,
-0.013887475244700909,
-0.015095067210495472,
-0.062208425253629684,
0.03823592886328697,
-0.0024993547704070807,
-0.021482320502400398,
0.14665453135967255,
0.004242550581693649,
0.026207977905869484,
-0.029335305094718933,
0.021610094234347343,
... | 0.066709 |
storage will be mounted. - `accessMode` (`string: ReadWriteOnce`) - Type of access mode of the storage device. - `annotations` (`dictionary: {}`) - This value defines additional annotations to add to the audit PVCs. This can either be YAML or a YAML-formatted multi-line templated string. ```yaml annotations: kubernetes... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.012105644680559635,
0.045191191136837006,
-0.044343747198581696,
0.003579973243176937,
0.01014271005988121,
-0.007328134961426258,
0.022983228787779808,
-0.00945818517357111,
0.10519394278526306,
-0.011520873755216599,
0.03565776348114014,
-0.04942513629794121,
0.01152518205344677,
0.002... | 0.103095 |
deploy to create a highly available cluster of Vault servers. - `updatePartition` (`int: 0`) - If an updatePartition is specified, all Pods with an ordinal that is greater than or equal to the partition will be updated when the StatefulSet’s `.spec.template` is updated. If set to `0`, this disables partition updates. F... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.010497692041099072,
0.03405064716935158,
0.039991170167922974,
-0.014234501868486404,
-0.014289222657680511,
-0.016731198877096176,
-0.04051016643643379,
-0.0204983651638031,
0.0616418682038784,
0.008459212258458138,
0.012121560052037239,
-0.01892155595123768,
0.03429585322737694,
-0.039... | 0.081703 |
only route to the active pod in a Vault HA cluster. - `serviceNodePort` (`int: null`) - Sets the Node Port value when using `serviceType: NodePort` on the Vault UI service. - `externalPort` (`int: 8200`) - Sets the external port value of the service. - `targetPort` (`int: 8200`) - Sets the target port value of the serv... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.010636861436069012,
0.007327589206397533,
-0.031399939209222794,
-0.027925394475460052,
-0.03206734359264374,
-0.01662074215710163,
-0.020935552194714546,
-0.03304550051689148,
0.009062115103006363,
0.027546752244234085,
0.012777027674019337,
0.0016853440320119262,
0.02852400578558445,
0... | 0.063613 |
pod ip. - `daemonSet` - Values that configure the Vault CSI Provider daemonSet. - `updateStrategy` - Values that configure the Vault CSI Provider update strategy. - `type` (`string: "RollingUpdate"`) - The [type of update strategy](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.011190902441740036,
0.04285493865609169,
0.007050675339996815,
-0.052633531391620636,
0.00736420089378953,
-0.0014671116368845105,
-0.022232184186577797,
-0.012480223551392555,
0.07065173983573914,
0.05039805546402931,
0.0432998463511467,
-0.01757897436618805,
0.015028451569378376,
-0.05... | 0.117862 |
initial delay of the liveness probe when the container starts. - `failureThreshold` (`int: 2`) - When set to a value, configures how many probe failures will be tolerated by Kubernetes. - `periodSeconds` (`int: 5`) - When set to a value, configures how often (in seconds) to perform the probe. - `successThreshold` (`int... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
0.024870408698916435,
0.018317939713597298,
-0.015842949971556664,
0.015901822596788406,
0.018725929781794548,
-0.08687193691730499,
-0.02816401980817318,
-0.02327638305723667,
0.046376314014196396,
0.019034553319215775,
0.02845831587910652,
-0.0711936429142952,
0.03491394594311714,
0.0207... | 0.055806 |
chart can be found [here](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack). More information can be found here in the [these](https://github.com/prometheus-operator/prometheus-operator) [repositories](https://github.com/prometheus-operator/kube-prometheus) - `selectors` (`dict... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/configuration.mdx | main | vault | [
-0.03548450767993927,
0.044816888868808746,
-0.015433481894433498,
-0.022090300917625427,
-0.014538689516484737,
-0.07821933180093765,
-0.060120511800050735,
-0.00029500393429771066,
0.04802553355693817,
0.01184006966650486,
0.01571398600935936,
-0.07802043855190277,
0.04531005769968033,
-... | 0.168329 |
# Vault Enterprise license management You can use this Helm chart to deploy Vault Enterprise by following a few extra steps around licensing. ~> \*\*Note:\*\* As of Vault Enterprise 1.8, the license must be specified via HCL configuration or environment variables on startup, unless the Vault cluster was created with an... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/enterprise.mdx | main | vault | [
0.08199086040258408,
0.0598156563937664,
-0.016429521143436432,
-0.12341324239969254,
-0.0314909890294075,
0.03027389943599701,
-0.03488307446241379,
-0.0009921995224431157,
0.07517080008983612,
-0.006992205511778593,
-0.01812463440001011,
-0.06612163037061691,
0.06595499813556671,
-0.0102... | -0.007757 |
# Helm chart @include 'helm/version.mdx' The [Vault Helm chart](https://github.com/hashicorp/vault-helm) is the recommended way to install and configure Vault on Kubernetes. In addition to running Vault itself, the Helm chart is the primary method for installing and configuring Vault to integrate with other services su... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/index.mdx | main | vault | [
0.11842246353626251,
0.06825108826160431,
-0.009192840196192265,
-0.09597554057836533,
0.003135120728984475,
0.01714836247265339,
-0.11579321324825287,
0.056457892060279846,
0.0534479133784771,
0.024945449084043503,
0.008025114424526691,
-0.01928231306374073,
0.05601194128394127,
-0.007690... | -0.026873 |
# Configure Vault Helm using Terraform Terraform may also be used to configure and deploy the Vault Helm chart, by using the [Helm provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs). For example, to configure the chart to deploy [HA Vault with integrated storage (raft)](/vault/docs/platform/k... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/terraform.mdx | main | vault | [
0.05951957777142525,
0.08553960919380188,
-0.026356583461165428,
-0.04399082064628601,
-0.03774131089448929,
-0.018211953341960907,
-0.06648939102888107,
0.009523136541247368,
0.03916032239794731,
0.04432114213705063,
0.00171881343703717,
-0.06739669293165207,
0.04663678631186485,
-0.03872... | -0.031142 |
# Run Vault on Openshift @include 'helm/version.mdx' The following documentation describes installing, running, and using Vault and \*\*Vault Agent Injector\*\* on OpenShift. The recommended method to access Vault securely on OpenShift is through the [Vault Secrets Operator](/vault/docs/deploy/kubernetes/vso/). Through... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/openshift.mdx | main | vault | [
0.08763258159160614,
0.035440895706415176,
-0.05997547507286072,
-0.03625916317105293,
0.03815754875540733,
0.024664785712957382,
-0.0840015783905983,
0.025791553780436516,
0.0232139490544796,
-0.02521543949842453,
-0.03481839597225189,
-0.009789269417524338,
0.02265738882124424,
-0.008998... | 0.041445 |
a Vault cluster using the Raft integrated storage backend. Install the latest Vault Helm chart in HA Raft mode: ```shell-session $ helm install vault hashicorp/vault \ --create-namespace \ --namespace vault \ --set='global.openshift=true' \ --set='server.ha.enabled=true' \ --set='server.ha.raft.enabled=true' ``` Initia... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/openshift.mdx | main | vault | [
0.032283589243888855,
0.039258923381567,
-0.0785464271903038,
0.021670494228601456,
0.00014615367399528623,
-0.12078270316123962,
-0.031194360926747322,
0.002869440708309412,
0.01844782382249832,
-0.026812328025698662,
0.04099724814295769,
-0.03566224128007889,
-0.0012251766165718436,
-0.0... | 0.064913 |
# Run Vault on Kubernetes Vault works with Kubernetes in various modes: `dev`, `standalone`, `ha`, and `external`. @include 'helm/version.mdx' ## Helm chart The [Vault Helm chart](https://github.com/hashicorp/vault-helm) is the recommended way to install and configure Vault on Kubernetes. In addition to running Vault i... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/run.mdx | main | vault | [
0.0712612196803093,
0.020310718566179276,
-0.021202366799116135,
-0.08509280532598495,
-0.02372262440621853,
-0.0065116058103740215,
-0.09274683892726898,
0.04318965971469879,
0.049934785813093185,
-0.001973310951143503,
-0.007842731662094593,
0.008362531661987305,
0.06765566021203995,
-0.... | 0.030551 |
install vault hashicorp/vault \ --set "injector.externalVaultAddr=http://external-vault:8200" ``` Refer to the [Integrate a Kubernetes Cluster with an External Vault](/vault/tutorials/kubernetes/kubernetes-external-vault) tutorial to learn how to use an external Vault within a Kubernetes cluster. ### View the Vault UI ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/run.mdx | main | vault | [
0.06052453815937042,
0.06253164261579514,
-0.02936909906566143,
-0.03150888904929161,
-0.028617635369300842,
0.004101705737411976,
-0.11646219342947006,
0.05371618643403053,
0.05246083065867424,
0.00368260289542377,
-0.009140897542238235,
-0.05257031321525574,
0.026681410148739815,
-0.0083... | 0.039332 |
environment variables that are defined in each Vault server pod. ##### Create the secret First, create a secret with your KMS access key/secret: ```shell-session $ kubectl create secret generic kms-creds \ --from-literal=AWS\_ACCESS\_KEY\_ID="${AWS\_ACCESS\_KEY\_ID?}" \ --from-literal=AWS\_SECRET\_ACCESS\_KEY="${AWS\_S... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/run.mdx | main | vault | [
0.07572334259748459,
0.08176564425230026,
-0.014865930192172527,
-0.030961422249674797,
0.006955003831535578,
-0.00806554313749075,
0.011564870364964008,
0.012027249671518803,
0.07464492321014404,
0.03252704069018364,
-0.006343242712318897,
-0.09481534361839294,
0.0930226594209671,
-0.0346... | -0.027072 |
any persisted data. If Vault is not deployed using `ha` mode, the single Vault server may be deleted by running: ```shell-session $ kubectl delete pod ``` If you deployed Vault in high availability (`ha`) mode, you must upgrade your standby pods before upgrading the active pod: 1. Before deleting the standby pod, remov... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/run.mdx | main | vault | [
0.05686841532588005,
0.05618626996874809,
-0.009420404210686684,
0.0009300545789301395,
0.0241183303296566,
-0.03244112804532051,
-0.05190169811248779,
-0.05749530345201492,
0.028298797085881233,
0.007425914518535137,
0.01623445563018322,
0.08001410961151123,
0.03348955512046814,
-0.068986... | -0.006459 |
used to front Vault, they should not terminate TLS. This way traffic is always encrypted in transit to Vault and minimizes risks introduced by intermediate layers. See the [official documentation](/vault/docs/platform/k8s/helm/examples/standalone-tls/) for example on configuring Vault Helm to use TLS. \_Single Tenancy.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/run.mdx | main | vault | [
0.004367287736386061,
0.13449658453464508,
-0.01310417428612709,
-0.06277016550302505,
-0.0063336873427033424,
-0.07215649634599686,
-0.04783383756875992,
-0.004391069523990154,
0.09849173575639725,
0.029762104153633118,
-0.023817535489797592,
0.044658124446868896,
0.04208048805594444,
-0.... | -0.026446 |
# Standalone server with audit storage @include 'helm/version.mdx' The below `values.yaml` can be used to set up a single server Vault cluster with auditing enabled. ```yaml server: standalone: enabled: true config: | listener "tcp" { tls\_disable = true address = "[::]:8200" cluster\_address = "[::]:8201" } storage "f... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/standalone-audit.mdx | main | vault | [
0.06032242253422737,
0.05261540785431862,
-0.041679926216602325,
-0.011813403107225895,
0.02218053676187992,
-0.04270235821604729,
-0.04361291602253914,
-0.04099216312170029,
0.1028546616435051,
0.011351265013217926,
0.024568211287260056,
-0.015209009870886803,
0.0626484602689743,
-0.01329... | 0.044123 |
# Highly available Vault Enterprise performance clusters with integrated storage (Raft) @include 'helm/version.mdx' The following is an example of creating a performance cluster using Vault Helm. For more information on Disaster Recovery, [see the official documentation](/vault/docs/enterprise/replication/). -> For lic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/enterprise-perf-with-raft.mdx | main | vault | [
0.07680345326662064,
0.05451606959104538,
-0.054823387414216995,
-0.05696485564112663,
-0.00160030007828027,
-0.04452046379446983,
-0.0928945392370224,
0.04379022866487503,
0.018956322222948074,
0.012985290959477425,
0.007080319337546825,
0.003591373562812805,
0.09313388168811798,
-0.03122... | 0.067189 |
kubectl delete pod vault-secondary-1 kubectl exec -ti vault-secondary-1 -- vault operator unseal kubectl delete pod vault-secondary-2 kubectl exec -ti vault-secondary-2 -- vault operator unseal ``` | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/enterprise-perf-with-raft.mdx | main | vault | [
0.02819705381989479,
0.0486551858484745,
0.02056480571627617,
-0.028462199494242668,
-0.040410418063402176,
-0.01598525047302246,
0.0117895333096385,
-0.08525359630584717,
0.06694483011960983,
-0.0317382887005806,
0.06384348124265671,
-0.05182242393493652,
0.041673630475997925,
-0.02549322... | 0.105115 |
# HA cluster with Raft and TLS The overview for [Integrated Storage and TLS](/vault/docs/concepts/integrated-storage#integrated-storage-and-tls) covers the various options for mitigating TLS verification warnings and bootstrapping your Raft cluster. Without proper configuration, you will see the following warning befor... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/ha-tls.mdx | main | vault | [
-0.07257024198770523,
0.11168275028467178,
-0.06846465915441513,
0.014081223867833614,
0.05676554515957832,
-0.11986232548952103,
0.008588949218392372,
-0.030578818172216415,
-0.002327264752238989,
-0.03182496130466461,
0.016202019527554512,
-0.02817842923104763,
0.12000148743391037,
0.046... | -0.033632 |
# Standalone server with TLS @include 'helm/version.mdx' This example can be used to set up a single server Vault cluster using TLS. 1. Create key & certificate using Kubernetes CA 2. Store key & cert into [Kubernetes secrets store](https://kubernetes.io/docs/concepts/configuration/secret/) 3. Configure helm chart to u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/standalone-tls.mdx | main | vault | [
0.01803607866168022,
0.05626659840345383,
-0.03280459716916084,
-0.07532389461994171,
-0.04976165294647217,
-0.035600777715444565,
-0.050132934004068375,
0.00913819670677185,
0.11411270499229431,
-0.0012172909919172525,
-0.02421613410115242,
-0.058645445853471756,
0.12404193729162216,
0.00... | -0.006741 |
create secret generic ${SECRET\_NAME} \ --namespace ${NAMESPACE} \ --from-file=vault.key=${TMPDIR}/vault.key \ --from-file=vault.crt=${TMPDIR}/vault.crt \ --from-file=vault.ca=${TMPDIR}/vault.ca # secret/vault-server-tls created ``` ## 3. helm configuration The below `custom-values.yaml` can be used to set up a single ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/standalone-tls.mdx | main | vault | [
0.025403006002306938,
0.08315427601337433,
-0.015221432782709599,
-0.02660706453025341,
-0.03390088677406311,
-0.03594813123345375,
-0.0391598604619503,
-0.010852745734155178,
0.13582850992679596,
0.0023926447611302137,
-0.0023138339165598154,
-0.08230597525835037,
0.08998939394950867,
0.0... | -0.031083 |
# Highly available Vault cluster with Consul @include 'helm/version.mdx' @include 'consul-dataplane-compat.mdx' The below `values.yaml` can be used to set up a five server Vault cluster using Consul as a highly available storage backend, Google Cloud KMS for Auto Unseal. ```yaml server: extraEnvironmentVars: GOOGLE\_RE... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/ha-with-consul.mdx | main | vault | [
0.02804436720907688,
-0.01476480346173048,
-0.021838055923581123,
-0.06486900895833969,
-0.04600058123469353,
-0.019695177674293518,
-0.06663160026073456,
0.025217078626155853,
0.01339674647897482,
0.03660864010453224,
0.008589551784098148,
-0.03373180329799652,
0.08365597575902939,
-0.002... | -0.032358 |
# Highly available Vault Enterprise disaster recovery clusters with integrated storage (Raft) @include 'helm/version.mdx' The following is an example of creating a disaster recovery cluster using Vault Helm. For more information on Disaster Recovery, [see the official documentation](/vault/docs/enterprise/replication/)... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/enterprise-dr-with-raft.mdx | main | vault | [
0.06295983493328094,
0.05233361944556236,
-0.03903048112988472,
-0.06462997198104858,
0.009090358391404152,
-0.03464105725288391,
-0.08851776272058487,
0.038922540843486786,
0.026324192062020302,
0.01342832576483488,
0.013301978819072247,
0.0010280907154083252,
0.09007015824317932,
-0.0250... | 0.061803 |
them using the primary unseal token after Kubernetes reschedules them: ```shell kubectl delete pod vault-secondary-1 kubectl exec -ti vault-secondary-1 -- vault operator unseal kubectl delete pod vault-secondary-2 kubectl exec -ti vault-secondary-2 -- vault operator unseal ``` | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/enterprise-dr-with-raft.mdx | main | vault | [
0.024593818932771683,
0.03524385020136833,
0.03186870366334915,
0.000781306647695601,
-0.03647653013467789,
0.0035087920259684324,
-0.02091638371348381,
-0.06584092229604721,
0.0999830961227417,
0.008603827096521854,
0.022392958402633667,
-0.011668901890516281,
0.0035361340269446373,
-0.02... | 0.14601 |
# Vault Agent Injector TLS with cert-manager The following instructions demonstrate how to configure the Vault Agent Injector to use certificates generated by [cert-manager](https://cert-manager.io/). This allows you to run multiple replicas of the Vault Agent Injector in a Kubernetes cluster. ## Prerequisites Install ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/injector-tls-cert-manager.mdx | main | vault | [
0.011412431485950947,
0.04103618487715721,
-0.04828398674726486,
-0.027934664860367775,
-0.012943552806973457,
-0.03555326908826828,
-0.04210996627807617,
-0.003696512896567583,
0.07630611211061478,
-0.03098210133612156,
-0.010958218947052956,
-0.08617819100618362,
0.09378201514482498,
0.0... | -0.00589 |
# Highly available Vault Enterprise cluster with integrated storage (Raft) @include 'helm/version.mdx' Integrated Storage (raft) can be enabled using the `server.ha.raft.enabled` value: ```shell helm install vault hashicorp/vault \ --set='server.image.repository=hashicorp/vault-enterprise' \ --set='server.image.tag=1.2... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/enterprise-with-raft.mdx | main | vault | [
0.043349385261535645,
0.060223307460546494,
-0.03313509002327919,
-0.06409902125597,
-0.03263014554977417,
-0.05658967047929764,
-0.07055780291557312,
0.045992378145456314,
0.02407856285572052,
0.012300457805395126,
0.010751386173069477,
-0.011329200118780136,
0.057773198932409286,
-0.0164... | 0.041746 |
# Vault Agent Injector TLS configuration @include 'helm/version.mdx' The following instructions demonstrate how to manually configure the Vault Agent Injector with self-signed certificates. ## Create a certificate authority (CA) First, create a private key to be used by our custom Certificate Authority (CA): ```shell $... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/injector-tls.mdx | main | vault | [
0.05133722722530365,
0.13440066576004028,
-0.06390123069286346,
-0.04354723542928696,
-0.02573828399181366,
-0.04725540429353714,
-0.07713782042264938,
0.038829438388347626,
0.017337793484330177,
-0.05872803181409836,
-0.0018809520406648517,
-0.07250676304101944,
0.1227802261710167,
0.0237... | -0.051972 |
# Highly available Vault cluster with integrated storage (Raft) @include 'helm/version.mdx' Integrated storage (raft) can be enabled using the `server.ha.raft.enabled` value: ```shell helm install vault hashicorp/vault \ --set='server.ha.enabled=true' \ --set='server.ha.raft.enabled=true' ``` Next, initialize and unsea... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/ha-with-raft.mdx | main | vault | [
0.05950682982802391,
0.026706980541348457,
-0.02569933421909809,
-0.03336111828684807,
-0.034498244524002075,
-0.07694391161203384,
-0.08093389868736267,
0.0005891807377338409,
0.006457303650677204,
-0.008476796559989452,
0.0032440440263599157,
-0.02842734009027481,
0.046714041382074356,
-... | 0.057513 |
# Bootstrapping Kubernetes auth method @include 'helm/version.mdx' In this example, we will walk through how to set up the [Kubernetes Auth Method](/vault/docs/auth/kubernetes). This assumes the following commands will be run inside a Vault pod running in Kubernetes. Exec into the Vault pod: ```bash kubectl exec -it va... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/helm/examples/kubernetes-auth.mdx | main | vault | [
0.07205905020236969,
0.04320111498236656,
-0.028438786044716835,
-0.1102246344089508,
-0.03600528836250305,
0.010026908479630947,
-0.0526915043592453,
0.03523029014468193,
0.04849229380488396,
0.03881320357322693,
-0.06616754829883575,
-0.03412208706140518,
0.07568396627902985,
0.019136026... | -0.044976 |
# Vault Agent Injector examples The following are different configuration examples to support a variety of deployment models. ~> A common mistake is to set the annotation on the Deployment or other resource. Ensure that the injector annotations are specified on the pod specification when using higher level constructs s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/examples.mdx | main | vault | [
0.03205224126577377,
-0.020665660500526428,
-0.008979673497378826,
-0.0251079760491848,
-0.04014917090535164,
-0.0031684646382927895,
-0.045399416238069534,
-0.039452362805604935,
0.05045768618583679,
0.014093400910496712,
-0.02086595818400383,
-0.006799566093832254,
0.06997279822826385,
0... | 0.09244 |
list of the Vault Agent configuration settings, [see the Agent documentation](/vault/docs/agent-and-proxy/agent/template#vault-agent-templates). ```yaml --- apiVersion: v1 kind: ServiceAccount metadata: name: app-example --- apiVersion: apps/v1 kind: Deployment metadata: name: app-example-deployment spec: replicas: 1 s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/examples.mdx | main | vault | [
0.0754539743065834,
0.030821627005934715,
-0.07943455129861832,
-0.051289159804582596,
-0.030067406594753265,
-0.06243104115128517,
-0.051147978752851486,
-0.012407959438860416,
0.028769969940185547,
-0.049017127603292465,
0.03882969543337822,
-0.011760824359953403,
0.058453209698200226,
0... | -0.000934 |
{{- end -}} spec: serviceAccountName: web containers: - name: web image: nginx ``` [pkiCert]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#pkicert [writeToFile]: https://github.com/hashicorp/consul-template/blob/main/docs/templating-language.md#writeToFile ## Cross namespace secret... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/examples.mdx | main | vault | [
-0.013902680948376656,
0.03687546029686928,
-0.043103817850351334,
-0.0434858612716198,
0.00036653055576607585,
-0.053650178015232086,
-0.03496570140123367,
-0.010694663971662521,
0.056608133018016815,
0.026870546862483025,
0.030573870986700058,
-0.048390068113803864,
-0.00794844888150692,
... | 0.104072 |
# Vault Agent Injector The Vault Agent Injector alters pod specifications to include Vault Agent containers that render Vault secrets to a shared memory volume using [Vault Agent Templates](/vault/docs/agent-and-proxy/agent/template). By rendering secrets to a shared volume, containers within the pod can consume Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/index.mdx | main | vault | [
0.005792316514998674,
0.06828330457210541,
-0.023547710850834846,
-0.021521413698792458,
0.006258382461965084,
-0.03904777765274048,
-0.012886859476566315,
-0.008020622655749321,
0.08980324864387512,
0.014166461303830147,
-0.017063414677977562,
-0.03188842162489891,
0.046992227435112,
-0.0... | 0.116219 |
format of the rendered secret using the annotation. For example the following secret will be rendered to `/vault/secrets/foo.txt`: ```yaml vault.hashicorp.com/agent-inject-secret-foo.txt: database/roles/app vault.hashicorp.com/role: 'app' ``` The secret unique name must consist of alphanumeric characters, `.`, `\_` or ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/index.mdx | main | vault | [
-0.014483842067420483,
0.08501657098531723,
-0.07713782787322998,
-0.02462070807814598,
-0.0014790118439123034,
-0.0365995429456234,
-0.04270411655306816,
0.06258933246135712,
0.049090441316366196,
-0.014251403510570526,
0.022861337289214134,
-0.0203008484095335,
0.02987496554851532,
0.018... | 0.040826 |
# Vault Agent Injector annotations The following are the available annotations for the injector. These annotations are organized into two sections: agent and vault. All of the annotations below change the configurations of the Vault Agent containers injected into the pod. ## Agent annotations Agent annotations change t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/annotations.mdx | main | vault | [
0.06148843094706535,
0.06553364545106888,
-0.041548848152160645,
-0.023156799376010895,
0.034781314432621,
-0.04562992975115776,
-0.02710464969277382,
-0.0021407424937933683,
-0.010263588279485703,
-0.019436128437519073,
0.029437007382512093,
-0.018254008144140244,
0.01758071407675743,
0.0... | 0.099858 |
- configures where on the filesystem a secret will be rendered. To map a path to a specific secret, use the same unique secret name: `vault.hashicorp.com/secret-volume-path-SECRET-NAME`. For example, if a secret annotation `vault.hashicorp.com/agent-inject-secret-foobar` is configured, `vault.hashicorp.com/secret-volum... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/annotations.mdx | main | vault | [
0.06363662332296371,
0.008262508548796177,
-0.05364764481782913,
-0.014537569135427475,
0.006762150675058365,
-0.02915400080382824,
-0.04208427667617798,
0.06553644686937332,
0.03339262679219246,
-0.03398625925183296,
0.038029901683330536,
-0.01391433272510767,
0.03514009714126587,
0.02455... | 0.055535 |
configures the ephemeral storage limit on the Vault Agent containers. Defaults to unset, which disables ephemeral storage limits. Also available as a command-line option (`-ephemeral-storage-limit`) or environment variable (`AGENT\_INJECT\_EPHEMERAL\_LIMIT`) to set the default for all injected Agent containers. \*\*Not... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/annotations.mdx | main | vault | [
0.1059703379869461,
0.06218563765287399,
-0.04012221843004227,
-0.00775811867788434,
-0.04340200498700142,
-0.050514087080955505,
-0.042774539440870285,
0.004936126060783863,
0.052699796855449677,
0.0043364474549889565,
-0.012673747725784779,
-0.009632358327507973,
-0.01704541966319084,
-0... | 0.087843 |
- sets [shareProcessNamespace] in the Pod spec where Vault Agent is injected. Defaults to `false`. - `vault.hashicorp.com/agent-cache-enable` - configures Vault Agent to enable [caching](/vault/docs/agent-and-proxy/agent/caching). In Vault 1.7+ this annotation will also enable a Vault Agent persistent cache. This persi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/annotations.mdx | main | vault | [
0.0296799186617136,
-0.005569727625697851,
-0.07681084424257278,
-0.013560275547206402,
-0.024147534742951393,
-0.05099577084183693,
-0.01313040778040886,
-0.023089947178959846,
0.012267773039638996,
-0.028032656759023666,
0.026570003479719162,
0.06049330160021782,
0.0018227045657113194,
0... | 0.056199 |
for all injected Agents via the `AGENT\_INJECT\_VAULT\_CACERT\_BYTES` environment variable which takes a PEM-encoded certificate or bundle. - `vault.hashicorp.com/ca-key` - path of the CA public key used to verify Vault's TLS. - `vault.hashicorp.com/client-cert` - path of the client certificate used when communicating ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/annotations.mdx | main | vault | [
0.04059452563524246,
0.051376525312662125,
-0.03868616744875908,
0.013849585317075253,
-0.05902829021215439,
-0.0861947312951088,
-0.05589424818754196,
-0.021899955347180367,
0.07374892383813858,
-0.05544731393456459,
0.03850506991147995,
0.010202025063335896,
0.1334371268749237,
0.0280208... | -0.03924 |
# Install Vault Agent Injector The [Vault Helm chart](/vault/docs/platform/k8s/helm) is the recommended way to install and configure the Agent Injector in Kubernetes. ~> The Vault Agent Injector requires Vault 1.3.1 or greater. To install a new instance of Vault and the Vault Agent Injector, first add the Hashicorp hel... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/installation.mdx | main | vault | [
0.08310133218765259,
0.05869290605187416,
-0.011624311096966267,
-0.08489499986171722,
-0.02020340971648693,
-0.005546189844608307,
-0.07857691496610641,
0.003270979505032301,
0.0468284897506237,
-0.003748239716514945,
0.020716050639748573,
-0.03873220458626747,
0.05314435437321663,
0.0125... | 0.00227 |
With Manual TLS and multiple replicas, [injector.leaderElector.enabled](/vault/docs/platform/k8s/helm/configuration#enabled-2) can be set to `false` since leader determination is not necessary in this case. ## Namespace selector By default, the Vault Agent Injector will process all namespaces in Kubernetes except the s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/deploy/kubernetes/injector/installation.mdx | main | vault | [
-0.004060137551277876,
0.08044321835041046,
-0.002612037118524313,
-0.05833813175559044,
-0.05000141263008118,
-0.025422608479857445,
-0.02861638180911541,
-0.06793145835399628,
0.12050000578165054,
-0.016501063480973244,
0.00482529029250145,
-0.07139212638139725,
0.09480931609869003,
0.02... | -0.0117 |
# Google Cloud secrets engine The Google Cloud Vault secrets engine dynamically generates Google Cloud service account keys and OAuth tokens based on IAM policies. This enables users to gain access to Google Cloud resources without needing to create or manage a dedicated service account. The benefits of using this secr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
-0.08455494046211243,
-0.0057949647307395935,
0.054094962775707245,
-0.039444759488105774,
-0.061004504561424255,
0.011483099311590195,
0.05449116602540016,
-0.05371050536632538,
0.05783039331436157,
0.04523495212197304,
0.052487101405858994,
0.013077028095722198,
0.06469323486089706,
-0.0... | -0.003059 |
or pod service account can be used in place of specifying the credentials JSON file. For more information on authentication, see the [authentication section](#authentication) below. In some cases, you cannot set sensitive IAM security credentials in your Vault configuration. For example, your organization may require t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
0.007050300016999245,
0.011918691918253899,
-0.026258116587996483,
-0.02776547335088253,
-0.04406389594078064,
0.003031754167750478,
0.08876819163560867,
0.01957489363849163,
0.07067926228046417,
0.08969203382730484,
-0.015605426393449306,
-0.06480153650045395,
0.043557729572057724,
0.0925... | 0.075166 |
bindings=-<@.iam.gserviceaccount.com`. To configure a static account that generates OAuth2 access tokens (preferred): ```shell-session $ vault write gcp/static-account/my-token-account \ service\_account\_email="account@my-project.iam.gserviceaccount.com" \ secret\_type="access\_token" \ token\_scopes="https://www.goog... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
-0.032880112528800964,
0.032011307775974274,
-0.017215939238667488,
-0.015646228566765785,
-0.06612306833267212,
-0.04635758697986603,
0.05794624239206314,
-0.015480253845453262,
-0.007981659844517708,
0.05093856900930405,
0.007970411330461502,
-0.07997596263885498,
0.1123245432972908,
-0.... | -0.081803 |
\* \* SAT" ... ``` Scheduled root credential rotation can also set a [rotation\_window](/vault/api-docs/secret/gcp#rotation\_window) during which the scheduled rotation is allowed to occur. Vault will stop trying to rotate the credential once the window expires. For example, the following command tells Vault to rotate ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
-0.0055262986570596695,
0.033165864646434784,
-0.03952248394489288,
-0.02408137172460556,
-0.08079244196414948,
0.004608987830579281,
-0.04589894413948059,
-0.012852824293076992,
0.042007237672805786,
0.007128340657800436,
-0.005919210612773895,
0.06310093402862549,
0.08660346269607544,
0.... | -0.083453 |
account keys quota limits GCP IAM has a hard limit (currently 10) on the number of Service Account keys. Attempts to generate more keys will result in an error. If you find yourself running into this limit, consider the following: - Have shorter TTLs or revoke access earlier. If you are not using past Service Account k... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
-0.057101670652627945,
-0.03167944774031639,
-0.012550268322229385,
-0.0584755577147007,
-0.08268614113330841,
-0.0012120753526687622,
0.06302396953105927,
0.015220420435070992,
0.04675033316016197,
0.07339438050985336,
0.013439753092825413,
-0.03690490126609802,
0.13046680390834808,
-0.00... | -0.008854 |
attributes when reading responses for the access tokens secrets endpoint (i.e. from `gcp/token/$roleset`). See the [documentation for access tokens](#access-tokens) to see the new format for the response. - Be aware of leftover leases from previous versions. While these old leases will still be revocable, they will not... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcp.mdx | main | vault | [
-0.052007876336574554,
0.03901335224509239,
0.04530714079737663,
0.0606149323284626,
0.019595902413129807,
0.009916352108120918,
0.011430819518864155,
-0.06000175327062607,
0.012886817567050457,
-0.01610281504690647,
0.013058357872068882,
0.04463835433125496,
0.009081712923943996,
-0.02693... | 0.001523 |
# AWS secrets engine The AWS secrets engine generates AWS access credentials dynamically based on IAM policies. This generally makes working with AWS IAM easier, since it does not involve clicking in the web UI. Additionally, the process is codified and mapped to internal auth methods (such as LDAP). The AWS IAM creden... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/aws.mdx | main | vault | [
-0.01879487931728363,
0.07718009501695633,
-0.0669415071606636,
-0.007526238448917866,
-0.018163464963436127,
-0.021036433055996895,
0.039811424911022186,
-0.02777915820479393,
0.11095499247312546,
0.02169470489025116,
0.02849344164133072,
-0.005754550453275442,
0.07502513378858566,
-0.001... | 0.018926 |
engine\*\*. 1. Click \*\*Save\*\* to enable the plugin. Configure the credentials that Vault uses to communicate with AWS to generate the IAM credentials: ```shell-session $ vault write aws/config/root \ access\_key=AKIAJWVN5Z4FOFT7NLNA \ secret\_key=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 \ region=us-east-1 ```  to rotate IAM user credentials, you must grant the following permissions on the IAM user itself: ```json ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/aws.mdx | main | vault | [
-0.05452363193035126,
0.03861973434686661,
-0.07639791816473007,
-0.01532586570829153,
-0.0697387233376503,
-0.02468748763203621,
0.07801926881074905,
-0.008717803284525871,
0.07291392982006073,
0.048110682517290115,
0.02871081419289112,
-0.03758551925420761,
0.07620426267385483,
0.0664566... | 0.082678 |
documentation](/vault/api-docs/secret/aws#create-update-static-role) for more details on the fields associated with the cross-account management of static roles. ## STS credentials The above demonstrated usage with `iam\_user` credential types. As mentioned, Vault also supports `assumed\_role`, `federation\_token`, and... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/aws.mdx | main | vault | [
0.0009003477753140032,
0.014855712652206421,
-0.05969160422682762,
0.007152467034757137,
-0.010902270674705505,
-0.028685083612799644,
0.03963230177760124,
-0.017901208251714706,
0.04122304171323776,
0.027403341606259346,
-0.004758620169013739,
-0.03623122349381447,
0.112042136490345,
0.02... | 0.049954 |
The `assumed\_role` credential type is typically used for cross-account authentication or single sign-on (SSO) scenarios. In order to use an `assumed\_role` credential type, you must configure outside of Vault: 1. An IAM role 2. IAM inline policies and/or managed policies attached to the IAM role 3. IAM trust policy at... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/aws.mdx | main | vault | [
0.020674511790275574,
-0.015538100153207779,
-0.030975621193647385,
0.00427863746881485,
-0.012157123535871506,
-0.024618200957775116,
0.039704687893390656,
-0.0018424397567287087,
0.04186581075191498,
-0.016069894656538963,
-0.003420739434659481,
-0.07199428975582123,
0.10256068408489227,
... | 0.019141 |
run `vault path-help aws` or with a subpath for interactive help output. ### STS federated token errors Vault generates STS tokens using the IAM credentials passed to `aws/config`. Those credentials must have two properties: - They must have permissions to call `sts:GetFederationToken`. - The capabilities of those cred... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/aws.mdx | main | vault | [
0.023948950693011284,
0.023464083671569824,
-0.07163035869598389,
0.0030782772228121758,
-0.03338054195046425,
-0.061224259436130524,
-0.03523917868733406,
-0.011964245699346066,
0.05499763414263725,
-0.011603998020291328,
-0.011776206083595753,
-0.05666932463645935,
0.07378414273262024,
0... | 0.000993 |
# KMIP secrets engine @include 'alerts/enterprise-and-hcp.mdx' KMIP secrets engine requires [Vault Enterprise](https://www.hashicorp.com/products/vault/pricing) with the Advanced Data Protection (ADP) module. The KMIP secrets engine allows Vault to act as a [Key Management Interoperability Protocol][kmip-spec] (KMIP) s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip.mdx | main | vault | [
0.003326814156025648,
0.029368124902248383,
-0.008901349268853664,
-0.07449951022863388,
-0.02734619937837124,
-0.025328010320663452,
0.012241707183420658,
-0.06964433193206787,
0.0652371272444725,
-0.06239849328994751,
-0.002676300937309861,
0.05214303731918335,
0.05909855663776398,
-0.04... | 0.113571 |
Certificate Authority for Client Certificates When the KMIP Secrets Engine is initially configured, Vault generates a KMIP Certificate Authority (CA) whose only purpose is to authenticate KMIP client certificates. Vault uses the internal KMIP CA to generate certificates for clients authenticating to Vault with the KMIP... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip.mdx | main | vault | [
-0.04066484421491623,
0.033802490681409836,
0.0162440687417984,
-0.030733101069927216,
-0.06262719631195068,
-0.05908883735537529,
0.01380931492894888,
-0.03345084190368652,
0.1207290068268776,
-0.03224505856633186,
-0.02222604863345623,
-0.05240173637866974,
0.11401155591011047,
0.0662071... | -0.036025 |
CLI to create a client certificate CSR in PEM format. 2. Sign the client certificate. This returns the CA Chain and the certificate, but not the private key, which never leaves the KMIP client. ```text $ vault write kmip/scope/my-service/role/admin/credential/sign csr="$(cat my-csr.pem)" Key Value --- ----- ca\_chain [... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip.mdx | main | vault | [
-0.009356826543807983,
0.09304353594779968,
-0.005906055681407452,
-0.03891181945800781,
-0.024135148152709007,
-0.019281720742583275,
0.019771477207541466,
-0.0029131886549293995,
0.12444955110549927,
-0.04965386912226677,
0.0562950000166893,
-0.07473720610141754,
0.1318683624267578,
0.01... | -0.140053 |
# MongoDB atlas secrets engine The MongoDB Atlas secrets engine generates Programmatic API keys. The created MongoDB Atlas secrets are time-based and are automatically revoked when the Vault lease expires, unless renewed. Vault will create a Programmatic API key for each lease that provide appropriate access to the def... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/mongodbatlas.mdx | main | vault | [
-0.071784608066082,
0.07808561623096466,
-0.07593678683042526,
0.057037122547626495,
-0.015120530501008034,
-0.05683029443025589,
-0.08580511808395386,
-0.011997900903224945,
0.0592728853225708,
0.0009721620590426028,
0.018366508185863495,
0.05204368010163307,
0.028132515028119087,
-0.0152... | 0.037009 |
(these are noted in the MongoDB Atlas API documentation). Create a Vault role for a MongoDB Atlas Programmatic API Key by mapping appropriate arguments to the organization or project designated: - Organization API Key: Set `organization\_id` argument with the appropriate [Organization Level Roles](https://www.mongodb.c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/mongodbatlas.mdx | main | vault | [
-0.006518235430121422,
0.05198600888252258,
-0.08678856492042542,
-0.012034723535180092,
-0.017291633412241936,
-0.0793992280960083,
-0.059108808636665344,
-0.004507510922849178,
0.026950819417834282,
-0.010008431039750576,
-0.0412515364587307,
-0.04685836285352707,
0.09464574605226517,
0.... | -0.016864 |
# Google Cloud KMS secrets engine The Google Cloud KMS Vault secrets engine provides encryption and key management via [Google Cloud KMS][kms]. It supports management of keys, including creation, rotation, and revocation, as well as encrypting and decrypting data with managed keys. This enables management of KMS keys t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcpkms.mdx | main | vault | [
-0.03529238700866699,
0.02817012183368206,
-0.0007064911187626421,
-0.016318967565894127,
-0.044827792793512344,
-0.015235337428748608,
-0.019217485561966896,
-0.026458492502570152,
0.02667168341577053,
0.0259841401129961,
0.016272930428385735,
0.019514886662364006,
0.07246717065572739,
-0... | -0.022651 |
crypto key version to become the primary. In practice, it is usually much shorter. Be sure to issue a read operation and verify the key version if you require new data to be encrypted with this key. Key Value --- ----- key\_version 2 ``` As the message says, rotation is not immediate. Depending on a number of factors, ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcpkms.mdx | main | vault | [
-0.0036934001836925745,
0.042685367166996,
-0.0423186831176281,
-0.03301016241312027,
-0.02207113802433014,
-0.02912886254489422,
-0.037934087216854095,
0.015116121619939804,
0.07315534353256226,
0.002780857030302286,
0.03567475453019142,
0.06003613397479057,
0.0381055511534214,
-0.0386455... | -0.1024 |
signing. In this model Google Cloud manages the key ring and exposes the public key via an API endpoint. A message or digest is signed with the corresponding private key, and can be verified by anyone with the corresponding public key. | Purpose | Supported Algorithms | | --- | --- | | `asymmetric_sign` | `rsa_sign_pss... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcpkms.mdx | main | vault | [
-0.022645484656095505,
-0.012002420611679554,
-0.04615243151783943,
-0.06379050016403198,
-0.006892147473990917,
-0.05969013273715973,
0.011391092091798782,
-0.030798768624663353,
0.06433974951505661,
0.025342803448438644,
0.004166406113654375,
-0.009618550539016724,
0.08195777982473373,
-... | -0.080109 |
key, or use an existing Cloud KMS key that is backed by an HSM. \*\*How much does this cost?\*\* The plugin is free and open source. KMS costs vary by key type and the number of operations. Please see the [Cloud KMS pricing page][kms-pricing] for more details. ## Help & support The Google Cloud KMS Vault secrets engine... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/gcpkms.mdx | main | vault | [
-0.04788341000676155,
0.007359442301094532,
-0.001007850980386138,
-0.011671164073050022,
-0.031267549842596054,
-0.007181494031101465,
-0.055871449410915375,
-0.014978053979575634,
-0.0174274779856205,
0.0646028220653534,
0.009566324763000011,
-0.029425201937556267,
0.07245971262454987,
-... | -0.0231 |
# KMIP profiles version 1.4 This document specifies conformance clauses in accordance with the OASIS TC Process ([TC-PROC section 2.18 paragraph 8a][tc-proc-2.18] ) for the KMIP Specification ([KMIP-SPEC 12.1 and 12.2][kmip-spec]) for a KMIP server or KMIP client through profiles that define the use of KMIP objects, at... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip-profiles.mdx | main | vault | [
-0.0036701273638755083,
0.02861320786178112,
0.025427022948861122,
-0.0802338570356369,
-0.05792754516005516,
-0.031164642423391342,
0.058207571506500244,
-0.05638556554913521,
0.05159837380051613,
-0.014026936143636703,
0.01653936877846718,
-0.010332424193620682,
0.12997472286224365,
0.00... | 0.008673 |
✅ | | | Get Attributes [KMIP-SPEC 4.12][kmip-spec-4.12] | ✅ | | | Get Attribute List [KMIP-SPEC 4.13][kmip-spec-4.13] | ✅ | | | Add Attribute [KMIP-SPEC 4.14][kmip-spec-4.14] | ✅ | | | Modify Attribute [KMIP-SPEC 4.15][kmip-spec-4.15] | ✅ | Vault 1.12 | | Delete Attribute [KMIP-SPEC 4.16][kmip-spec-4.16] | ✅ | Vault 1.... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip-profiles.mdx | main | vault | [
0.015655148774385452,
0.04432997852563858,
0.023278556764125824,
-0.04341266304254532,
0.014351861551404,
-0.0015220576897263527,
0.07654054462909698,
-0.05305503308773041,
0.013478146865963936,
0.012547515332698822,
0.09838151931762695,
-0.044373515993356705,
0.0698586106300354,
-0.063391... | -0.042114 |
clause within [KMIP-SPEC][kmip-spec] provided it does not conflict with any other clause within the section [Symmetric Key Lifecycle Server][lifecycle-server] 7. MAY support extensions outside the scope of this standard (e.g., vendor extensions, conformance clauses) that do not contradict any KMIP requirements. ## [Bas... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip-profiles.mdx | main | vault | [
-0.06946992129087448,
-0.009403795003890991,
0.029041854664683342,
-0.08062706887722015,
-0.021498000249266624,
-0.037819355726242065,
0.022190898656845093,
-0.06298229843378067,
0.00015568436356261373,
0.03016209974884987,
0.035166315734386444,
-0.0050454880110919476,
0.04219150170683861,
... | -0.008158 |
vendor extensions, conformance clauses) that do not contradict any KMIP requirements. ## [Advanced cryptographic server][advanced-cryptographic-server] 1. SHALL conform to the [Baseline Server][baseline-server] 2. Supports the following client-to-server operations: | Operation | Supported | Notes | | ------------------... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip-profiles.mdx | main | vault | [
-0.05796651169657707,
0.015758801251649857,
-0.03151143342256546,
-0.11019305884838104,
-0.026573408395051956,
-0.0800660103559494,
0.00423419801518321,
-0.0126357926055789,
0.06823107600212097,
-0.0015719094080850482,
0.046121444553136826,
0.02087417244911194,
0.04480091854929924,
0.02909... | -0.012278 |
https://docs.oasis-open.org/kmip/spec/v1.4/errata01/os/kmip-spec-v1.4-errata01-os-redlined.html#\_Toc490660874 [kmip-spec-4.35]: https://docs.oasis-open.org/kmip/spec/v1.4/errata01/os/kmip-spec-v1.4-errata01-os-redlined.html#\_Toc490660875 [kmip-spec-4.36]: https://docs.oasis-open.org/kmip/spec/v1.4/errata01/os/kmip-sp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kmip-profiles.mdx | main | vault | [
-0.05555318295955658,
-0.060337331146001816,
0.028835806995630264,
0.0162428617477417,
0.009898648597300053,
0.03203064948320389,
-0.018840862438082695,
-0.017509961500763893,
-0.0022326759062707424,
-0.0032692148815840483,
0.09791558235883713,
0.05147214233875275,
-0.023355908691883087,
-... | 0.134538 |
# Secrets engines Secrets engines are components which store, generate, or encrypt data. Secrets engines are incredibly flexible, so it is easiest to think about them in terms of their function. Secrets engines are provided some set of data, they take some action on that data, and they return a result. Some secrets eng... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/index.mdx | main | vault | [
-0.07986976206302643,
-0.00965468492358923,
-0.04955099895596504,
0.02290676161646843,
-0.027549056336283684,
-0.02212485484778881,
-0.05591005086898804,
-0.010832752101123333,
0.0700211226940155,
-0.07795462012290955,
-0.02790311723947525,
0.08545123785734177,
-0.003032542997971177,
-0.05... | 0.058343 |
# Kubernetes secrets engine @include 'x509-sha1-deprecation.mdx' The Kubernetes Secrets Engine for Vault generates Kubernetes service account tokens, and optionally service accounts, role bindings, and roles. The created service account tokens have a configurable TTL and any objects created are automatically deleted wh... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kubernetes.mdx | main | vault | [
-0.02979692630469799,
-0.007146834395825863,
-0.0002638785808812827,
-0.05368087440729141,
-0.03647998347878456,
0.016740484163165092,
0.03892498090863228,
-0.028851378709077835,
0.11849464476108551,
0.000947765598539263,
0.005827651359140873,
0.02445230633020401,
0.056392915546894073,
-0.... | 0.078992 |
Vault will not be automatically managing roles or service accounts (see [Automatically Managing Roles and Service Accounts](#automatically-managing-roles-and-service-accounts)), then you will need to set up a service account that Vault will issue tokens for. ~> \*\*Note\*\*: It is highly recommended that the service ac... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kubernetes.mdx | main | vault | [
0.03510875627398491,
-0.017321869730949402,
-0.01590736210346222,
-0.03395466133952141,
-0.07428031414747238,
-0.030823297798633575,
0.01839258335530758,
-0.016196127980947495,
0.09988806396722794,
-0.0036016793455928564,
-0.024452097713947296,
-0.06907752901315689,
0.058915019035339355,
0... | 0.002113 |
status: {token: .data.service\_account\_token}}' ``` As a result, you can call `kubectl` directly: ```shell-session $ export VAULT\_ADDR=\*\*\* $ export VAULT\_TOKEN=$(vault login -token-only -method=ldap username=\*\*\*) $ export KUBECONFIG=kubeconfig.yml $ kubectl get namespaces ``` ~> \*\*Note\*\*: While this method... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kubernetes.mdx | main | vault | [
0.057553481310606,
-0.007068478036671877,
-0.006403174251317978,
0.03215746581554413,
-0.046129487454891205,
-0.06028054654598236,
-0.01102785300463438,
0.01516489777714014,
0.11800563335418701,
-0.02903771586716175,
-0.0009107617079280317,
-0.06278853118419647,
0.010775230824947357,
-0.05... | 0.040104 |
JSON or YAML rules for the generated role. ```shell-session $ vault write kubernetes/roles/auto-managed-sa-and-role \ allowed\_kubernetes\_namespaces="test" \ generated\_role\_rules='{"rules":[{"apiGroups":[""],"resources":["pods"],"verbs":["list"]}]}' ``` You can then get credentials in the same way as before. ```shel... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/kubernetes.mdx | main | vault | [
0.008502420969307423,
0.06701962649822235,
-0.049804989248514175,
-0.026093920692801476,
-0.06948748230934143,
0.029381077736616135,
0.018998878076672554,
0.008352154865860939,
0.061741914600133896,
0.028424249961972237,
-0.027524737641215324,
-0.09737645834684372,
0.06146041303873062,
0.0... | 0.0328 |
# AliCloud secrets engine The AliCloud secrets engine dynamically generates AliCloud access tokens based on RAM policies, or AliCloud STS credentials based on RAM roles. This generally makes working with AliCloud easier, since it does not involve clicking in the web UI. The AliCloud access tokens are time-based and are... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/alicloud.mdx | main | vault | [
-0.039619240909814835,
-0.009802212007343769,
-0.10831867158412933,
0.019513266161084175,
-0.048409849405288696,
0.0119987353682518,
0.022754911333322525,
-0.0355728454887867,
0.07777942717075348,
-0.04360220953822136,
0.03730717673897743,
0.0787544921040535,
0.05591007322072983,
-0.036343... | 0.076091 |
# TOTP secrets engine The TOTP secrets engine generates time-based credentials according to the TOTP standard. The secrets engine can also be used to generate a new key and validate passwords generated by that key. The TOTP secrets engine can act as both a generator (like Google Authenticator) and a provider (like the ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/totp.mdx | main | vault | [
-0.11461010575294495,
-0.04645878076553345,
-0.02633942849934101,
0.025547895580530167,
-0.0014799078926444054,
0.04091738536953926,
0.007271832320839167,
-0.06290549784898758,
0.0368393138051033,
-0.008622881025075912,
-0.006110387854278088,
0.045583538711071014,
0.0675663873553276,
-0.06... | 0.051829 |
# Nomad secrets engine @include 'x509-sha1-deprecation.mdx' Nomad is a simple, flexible scheduler and workload orchestrator. The Nomad secrets engine for Vault generates [Nomad](https://www.nomadproject.io/) ACL tokens dynamically based on pre-existing Nomad ACL policies. This page will show a quick start for this secr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/nomad.mdx | main | vault | [
-0.006899945437908173,
0.09431035071611404,
-0.08229334652423859,
-0.03722323477268219,
-0.024740679189562798,
0.007732850965112448,
-0.05736984685063362,
-0.038306791335344315,
0.00804982241243124,
-0.04032457247376442,
0.055804572999477386,
-0.011449938639998436,
0.11063984036445618,
0.0... | -0.04355 |
# Consul secrets engine @include 'x509-sha1-deprecation.mdx' The Consul secrets engine generates [Consul](https://www.consul.io/) API tokens dynamically based on Consul ACL policies. -> \*\*Note:\*\* See the Consul Agent [config documentation](/consul/docs/agent/config/config-files#acl-parameters) for details on how to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/consul.mdx | main | vault | [
-0.06646393984556198,
-0.006277617998421192,
-0.0857992097735405,
-0.03461093083024025,
-0.0360763743519783,
-0.07125190645456314,
-0.0496707484126091,
0.028080757707357407,
0.029421629384160042,
0.019460810348391533,
0.03240896388888359,
-0.017365729436278343,
0.043323125690221786,
0.0021... | 0.048218 |
$ vault write consul/roles/my-role \ service\_identities="myservice-1:dc1,dc2" \ service\_identities="myservice-2:dc1" Success! Data written to: consul/roles/my-role ``` 1. For Consul versions 1.4 and above, generate [a policy in Consul](/consul/tutorials/security/access-control-setup-production), and proceed to link i... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/consul.mdx | main | vault | [
0.029631223529577255,
0.007034767884761095,
-0.09526915848255157,
-0.021366512402892113,
-0.04743694141507149,
-0.040464553982019424,
0.010053770616650581,
0.03851322457194328,
0.044411491602659225,
0.016845041885972023,
0.015950554981827736,
-0.012584737502038479,
0.09722631424665451,
0.0... | -0.080583 |
# HCP Terraform secrets engine The HCP Terraform secrets engine for Vault generates [HCP Terraform](https://cloud.hashicorp.com/products/terraform) API tokens dynamically for Organizations, Teams, and Users. This page will show a quick start for this backend. For detailed documentation on every path, use `vault path-he... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/terraform.mdx | main | vault | [
-0.009102621115744114,
0.02202928625047207,
0.0006465241312980652,
-0.03073500283062458,
-0.04334993287920952,
-0.007974517531692982,
-0.09464073926210403,
-0.03113557957112789,
-0.0009321329416707158,
-0.010496323928236961,
-0.02461397647857666,
-0.04920618608593941,
0.012346142902970314,
... | 0.060288 |
permissions when a more narrowly-defined scope prevents Vault from issuing appropriate tokens or interferes with your intended workflows. ### Organization roles Generating a new Organization API token by reading the credentials in Vault or otherwise generating them on [app.terraform.io](https://app.terraform.io/session... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/terraform.mdx | main | vault | [
-0.010692179203033447,
0.044307515025138855,
0.008920912630856037,
0.0012376655358821154,
-0.03409107029438019,
-0.0715116411447525,
-0.03473350405693054,
-0.042725127190351486,
0.10982193052768707,
0.056375909596681595,
-0.04401518404483795,
0.014537440612912178,
0.052607323974370956,
0.0... | 0.008084 |
API limits Legacy Team roles to \*\*one active token at any given time\*\*. Generating a new Legacy Team API token by reading the credentials in Vault or otherwise generating them on [app.terraform.io](https://app.terraform.io/session) will effectively revoke \*\*any\*\* existing API token for that Team. Due to this be... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/terraform.mdx | main | vault | [
-0.04498216509819031,
0.05385500565171242,
0.0319029875099659,
-0.020433083176612854,
-0.04294542223215103,
-0.059708692133426666,
-0.04114018753170967,
-0.020906701683998108,
0.08360515534877777,
0.037552691996097565,
-0.023950787261128426,
0.01439104788005352,
0.10698622465133667,
0.0284... | -0.038549 |
# RabbitMQ secrets engine The RabbitMQ secrets engine generates user credentials dynamically based on configured permissions and virtual hosts. This means that services that need to access a virtual host no longer need to hardcode credentials. With every service accessing the messaging queue with unique credentials, au... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/rabbitmq.mdx | main | vault | [
0.03399123251438141,
-0.006600165739655495,
-0.03952356427907944,
0.03940824419260025,
-0.09131671488285065,
-0.011023931205272675,
0.03486132249236107,
-0.04153406247496605,
0.043683066964149475,
0.029817422851920128,
0.005037255585193634,
0.045179929584264755,
0.034585870802402496,
0.022... | 0.009134 |
# Cubbyhole secrets engine The `cubbyhole` secrets engine is used to store arbitrary secrets within the configured physical storage for Vault namespaced to a token. In `cubbyhole`, paths are scoped per token. No token can access another token's cubbyhole. When the token expires, its cubbyhole is destroyed. Also unlike ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/cubbyhole.mdx | main | vault | [
-0.06843848526477814,
0.03632073849439621,
-0.090524822473526,
0.0617053396999836,
-0.07920181006193161,
-0.005776465404778719,
-0.06747518479824066,
-0.0006984807550907135,
0.057934436947107315,
-0.04250147193670273,
-0.002061260864138603,
0.041094254702329636,
0.01374094095081091,
-0.063... | 0.117095 |
# Azure secrets engine The Azure secrets engine dynamically generates Azure service principals along with role and group assignments. Vault roles can be mapped to one or more Azure roles, and optionally group assignments, providing a simple, flexible way to manage the permissions granted to generated service principals... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
-0.03746834769845009,
0.004096682649105787,
-0.05123806744813919,
0.039103876799345016,
-0.05782851576805115,
0.0412621907889843,
-0.0024506407789885998,
-0.10346704721450806,
0.08941525965929031,
0.042615894228219986,
0.021189207211136818,
0.06407151371240616,
0.08969753980636597,
0.03576... | -0.081582 |
Alternatively, configure the audience claim value and the Client, Tenant and Subscription IDs for plugin workload identity federation: ```shell-session $ vault write azure/config \ subscription\_id=$AZURE\_SUBSCRIPTION\_ID \ tenant\_id=$AZURE\_TENANT\_ID \ client\_id=$AZURE\_CLIENT\_ID \ identity\_token\_audience=$TOKE... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
0.017538882791996002,
0.03702897951006889,
-0.0665002167224884,
0.037311188876628876,
0.00835391879081726,
-0.003441666718572378,
0.05573258548974991,
-0.04447486251592636,
0.07579253613948822,
0.09035664796829224,
0.009929700754582882,
-0.03919623792171478,
0.09431858360767365,
0.09719228... | -0.034595 |
set the rotation to occur every Saturday at midnight (00:00):: ```shell-session $ vault write azure/config \ ... rotation\_schedule="0 \* \* \* SAT" ... ``` Scheduled root credential rotation can also set a [rotation\_window](/vault/api-docs/secret/azure#rotation\_window) during which the scheduled rotation is allowed ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
0.03341013938188553,
0.03386900573968887,
-0.0775410383939743,
-0.002360235434025526,
-0.07139476388692856,
0.01958891749382019,
-0.03901699185371399,
-0.05209355801343918,
0.08433269709348679,
0.0678531676530838,
-0.011295555159449577,
0.048745106905698776,
0.08835787326097488,
0.06153427... | -0.110277 |
matter as it will be overwritten", "role\_id": "/subscriptions//providers/Microsoft.Authorization/roleDefinitions/", "scope": "/subscriptions//resourceGroups/Database" } ] $ cat az\_groups.json [ { "group\_name": "foo" }, { "group\_name": "This won't matter as it will be overwritten", "object\_id": "a6a834a6-36c3-4575-... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
-0.0577639676630497,
0.0474085658788681,
-0.0571046881377697,
0.08165013045072556,
-0.027264393866062164,
-0.015134833753108978,
0.062203098088502884,
-0.13238170742988586,
0.10242921859025955,
0.06502478569746017,
0.038645025342702866,
0.039566125720739365,
0.11104708909988403,
0.07005766... | -0.0123 |
an API proxy or gateway if you need to limit Vault API exposure. 1. Configure a [federated identity credential](https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-create-trust?pivots=identity-wif-apps-methods-azp#configure-a-federated-identity-credential-on-an-app) on a dedicated applicati... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
-0.03467114269733429,
0.019942939281463623,
-0.05487917736172676,
-0.0017715091817080975,
-0.029211467131972313,
-0.04470515251159668,
0.021896515041589737,
-0.043032851070165634,
0.1061626523733139,
0.03945080190896988,
-0.002554246922954917,
-0.015858186408877373,
0.11467407643795013,
0.... | -0.007954 |
the object size is reached. This limit can be managed by reducing the role TTL, or by creating another Vault role against a different Azure service principal configured with the same permissions. ## Additional notes - \*\*If a referenced Azure role doesn't exist, a credential will not be generated.\*\* Service principa... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/azure.mdx | main | vault | [
0.011237320490181446,
-0.029257671907544136,
-0.02494914084672928,
0.02489972673356533,
-0.042981650680303574,
-0.014328282326459885,
-0.012809962965548038,
-0.057157911360263824,
0.08068742603063583,
0.049373071640729904,
0.0012912576785311103,
0.04175359010696411,
0.07445745915174484,
0.... | -0.043801 |
# MongoDB Atlas database secrets engine MongoDB Atlas is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for MongoDB Atlas databases. It cannot support rotating the root user's credentials because it uses a public and private... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mongodbatlas.mdx | main | vault | [
-0.06698563694953918,
0.040502600371837616,
-0.10050150752067566,
0.027240749448537827,
-0.05651025101542473,
-0.060424163937568665,
-0.08939052373170853,
0.01956089399755001,
0.025350000709295273,
-0.0026887611020356417,
-0.0161130391061306,
0.041150059551000595,
0.04776013270020485,
0.01... | -0.02957 |
security as an alternative to username and password authentication. The MongoDB Atlas database plugin can be used to manage client certificate credentials for MongoDB Atlas users by using `client\_certificate` [credential\_type](/vault/api-docs/secret/databases#credential\_type). See the [usage](/vault/docs/secrets/dat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mongodbatlas.mdx | main | vault | [
-0.07319144159555435,
0.10497961938381195,
-0.10569173842668533,
0.037147581577301025,
-0.0333745963871479,
-0.036761391907930374,
-0.04419465735554695,
0.046269144862890244,
0.04396098107099533,
-0.024819497019052505,
-0.06706807017326355,
0.03862036392092705,
0.04671013727784157,
0.04456... | 0.035579 |
# MySQL/MariaDB database secrets engine @include 'x509-sha1-deprecation.mdx' MySQL is one of the supported plugins for the database secrets engine. This plugin generates database credentials dynamically based on configured roles for the MySQL database, and also supports [Static Roles](/vault/docs/secrets/databases#stat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mysql-maria.mdx | main | vault | [
-0.006388454232364893,
-0.03601842001080513,
-0.07198209315538406,
-0.02886086516082287,
-0.08469058573246002,
0.006348018068820238,
-0.04376312345266342,
0.07043435424566269,
0.004102226812392473,
-0.058943238109350204,
-0.016521576792001724,
0.004676608368754387,
0.13467258214950562,
0.0... | -0.020022 |
the CLI because the shell will interpret the text between the backticks as something that must be executed. The easiest way to get around this is to encode the creation statement as Base64 and feed this to Vault. For example: ```shell-session $ vault write database/roles/my-role \ db\_name=mysql \ creation\_statements=... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/secrets/databases/mysql-maria.mdx | main | vault | [
0.028513966128230095,
0.003934348002076149,
-0.06629184633493423,
-0.060616038739681244,
-0.1050315871834755,
-0.027484269812703133,
-0.01417053397744894,
0.04602154716849327,
0.09049723297357559,
0.021905453875660896,
0.0072624292224645615,
0.002429450862109661,
0.17115454375743866,
-0.01... | -0.086348 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.