content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
## Step-01: PODs Introduction - What is a POD ? - What is a Multi-Container POD? ## Step-02: PODs Demo ### Step-02-01: Get Worker Nodes Status - Verify if kubernetes worker nodes are ready. ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project gcloud container clusters get... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/06-kubectl-imperative-k8s-pods/README.md | main | google-kubernetes-engine | [
0.012037830427289009,
0.006262847688049078,
0.03888346627354622,
-0.028576470911502838,
-0.013549533672630787,
-0.05614110827445984,
-0.00022041199554223567,
-0.001099486486054957,
0.0008707675733603537,
0.03847471624612808,
0.022179236635565758,
-0.0904294103384018,
0.0024772973265498877,
... | 0.128351 |
and Services\*\* on Google GKE Dashboard GCP Console ## Step-05: Interact with a Pod ### Step-05-01: Verify Pod Logs ```t # Get Pod Name kubectl get po # Dump Pod logs kubectl logs kubectl logs my-first-pod # Stream pod logs with -f option and access application to see logs kubectl logs kubectl logs -f my-first-pod ```... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/06-kubectl-imperative-k8s-pods/README.md | main | google-kubernetes-engine | [
0.004019563551992178,
-0.022187381982803345,
0.06993976980447769,
-0.04297228530049324,
0.006275890860706568,
-0.05521480366587639,
0.0033265266101807356,
-0.03385205194354057,
0.020853761583566666,
0.04575440660119057,
-0.02417287416756153,
-0.09146266430616379,
-0.025693189352750778,
0.0... | 0.075478 |
## Step-01: Introduction - Create GKE Standard GKE Cluster - Configure Google CloudShell to access GKE Cluster - Deploy simple Kubernetes Deployment and Kubernetes Load Balancer Service and Test - Clean-Up ## Step-02: Create Standard GKE Cluster - Go to Kubernetes Engine -> Clusters -> CREATE - Select \*\*GKE Standard ... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/02-Create-GKE-Cluster/README.md | main | google-kubernetes-engine | [
0.04199802875518799,
-0.005109881050884724,
0.01987500675022602,
-0.06473302841186523,
-0.04349628463387489,
-0.006910981144756079,
-0.05346217378973961,
-0.07265366613864899,
-0.019871698692440987,
0.0390956811606884,
-0.027731776237487793,
-0.08383321762084961,
-0.00885157473385334,
-0.0... | 0.052558 |
version kubectl version --short # Install kubectl (if not installed) gcloud components install kubectl # Configure kubectl gcloud container clusters get-credentials --zone --project gcloud container clusters get-credentials standard-cluster-1 --zone us-central1-c --project kdaida123 # Verify Kubernetes Worker Nodes kub... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/02-Create-GKE-Cluster/README.md | main | google-kubernetes-engine | [
0.0366838164627552,
-0.02324991300702095,
0.027512896806001663,
-0.053344666957855225,
0.03870103135704994,
-0.025863369926810265,
-0.02787596918642521,
-0.07246723026037216,
0.061852045357227325,
0.05928504467010498,
0.009754377417266369,
-0.1324332058429718,
-0.012065806426107883,
-0.073... | 0.071054 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, REGION, PROJECT gcloud container clusters get-creden... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/66-Kubernetes-Namespaces-LimitRange/README.md | main | google-kubernetes-engine | [
0.008518708869814873,
0.013505449518561363,
0.016713788732886314,
-0.04922318831086159,
-0.03663463890552521,
-0.002728652209043503,
-0.04074299335479736,
-0.03394046798348427,
0.055436018854379654,
0.04973972216248512,
-0.0011598037090152502,
-0.14845454692840576,
0.014508274383842945,
-0... | 0.078404 |
is 600m # Get & Describe Limits kubectl get limits -n qa kubectl describe limits default-cpu-mem-limit-range -n qa # List Services kubectl get svc -n qa # Access Application http:/// ``` ## Step-08: Demo-02: Update Deployment resources.limit=500m - \*\*File Name:\*\* 03-kubernetes-deployment.yaml ```t # Demo-02: Update... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/66-Kubernetes-Namespaces-LimitRange/README.md | main | google-kubernetes-engine | [
0.0132781732827425,
0.005988190416246653,
-0.04001476243138313,
0.003664865856990218,
-0.04642149433493614,
-0.05349922180175781,
-0.025626165792346,
0.014626902528107166,
0.04386528953909874,
0.05816396698355675,
-0.00044709586654789746,
-0.06392651051282883,
-0.037414442747831345,
-0.072... | 0.194374 |
## Step-00: Pre-requisites - We should have the two clusters created and ready - standard-cluster-private-1 - autopilot-cluster-private-1 ## Step-01: Introduction - Configure access to Multiple Clusters - Understand kube config file $HOME/.kube/config - Understand kubectl config command - kubectl config view - kubectl ... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/69-Access-To-Multiple-Clusters/README.md | main | google-kubernetes-engine | [
0.0663798451423645,
-0.027411747723817825,
0.029320092871785164,
-0.050952766090631485,
-0.0025663997512310743,
0.00028812538948841393,
-0.0001496238401159644,
-0.020814979448914528,
-0.03784964606165886,
0.05653825029730797,
0.03128613904118538,
-0.16943363845348358,
-0.00295294844545424,
... | 0.071216 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, REGION, PROJECT gcloud container clusters get-creden... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/46-GKE-Ingress-SSL-Policy/README.md | main | google-kubernetes-engine | [
-0.04312436655163765,
-0.0016418119193986058,
0.05206235870718956,
-0.043404124677181244,
-0.08291911333799362,
-0.03560381755232811,
-0.0009528140653856099,
-0.04451506584882736,
0.03159502148628235,
0.03800113499164581,
-0.059347182512283325,
-0.10571767389774323,
0.047359902411699295,
-... | 0.056971 |
## Step-01: Introduction - Install gcloud CLI on MacOS - Configure kubeconfig for kubectl on your local terminal - Verify if you are able to reach GKE Cluster using kubectl from your local terminal ## Step-02: Install gcloud cli on MacOS - [Install gcloud cli](https://cloud.google.com/sdk/docs/install-sdk#mac) ```t # V... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/03-gcloud-cli-install-macos/README.md | main | google-kubernetes-engine | [
-0.027548842132091522,
-0.021490097045898438,
0.06183727830648422,
-0.06617113202810287,
0.006391751114279032,
-0.0555870495736599,
-0.04476366564631462,
-0.04982578009366989,
0.014217684976756573,
0.015027472749352455,
0.04140280932188034,
-0.10055103152990341,
0.020243294537067413,
-0.05... | 0.007147 |
get nodes # Verify System Pod in kube-system Namespace kubectl -n kube-system get pods # Verify kubeconfig file cat $HOME/.kube/config kubectl config view ``` ## References - [gcloud CLI](https://cloud.google.com/sdk/gcloud) - [Install the Google Cloud CLI](https://cloud.google.com/sdk/docs/install-sdk#mac) | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/03-gcloud-cli-install-macos/README.md | main | google-kubernetes-engine | [
0.0039033645298331976,
0.004119850229471922,
0.04850435256958008,
-0.06028366833925247,
0.061405546963214874,
-0.052392274141311646,
0.01535470224916935,
-0.0676150843501091,
0.04083002731204033,
0.03867633640766144,
0.04582792520523071,
-0.12150384485721588,
0.024820245802402496,
-0.10425... | 0.055637 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, ZONE, PROJECT gcloud container clusters get-credenti... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/19-GKE-Headless-Service/README.md | main | google-kubernetes-engine | [
0.03600721433758736,
0.017160354182124138,
0.017881622537970543,
-0.0586758516728878,
-0.02213328331708908,
-0.02745966985821724,
-0.030706455931067467,
-0.04845660179853439,
0.029267359524965286,
0.062125109136104584,
0.007900340482592583,
-0.11650121957063675,
0.013785128481686115,
-0.05... | 0.093564 |
02-kube-manifests-curl ``` | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/19-GKE-Headless-Service/README.md | main | google-kubernetes-engine | [
0.004068948794156313,
0.021794360131025314,
0.056837234646081924,
-0.07502391189336777,
-0.05224015563726425,
-0.02053048461675644,
-0.0229656882584095,
-0.013875366188585758,
0.08899456262588501,
0.002565657952800393,
-0.01483377069234848,
-0.07695670425891876,
-0.05706196278333664,
-0.08... | 0.12727 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, ZONE, PROJECT gcloud container clusters get-credenti... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/26-GKE-PD-Volume-Snapshots-and-Restore/README.md | main | google-kubernetes-engine | [
-0.008326721377670765,
-0.0022958009503781796,
0.002394507173448801,
-0.08089876174926758,
-0.02810061164200306,
-0.014834887348115444,
-0.047388721257448196,
-0.05059428885579109,
0.00946336705237627,
0.01355693954974413,
0.008922811597585678,
-0.15123571455478668,
0.04307999461889267,
-0... | 0.051366 |
01-restore-pvc.yaml ```yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc-restore spec: dataSource: name: my-snapshot1 kind: VolumeSnapshot apiGroup: snapshot.storage.k8s.io storageClassName: standard-rwo accessModes: - ReadWriteOnce resources: requests: storage: 4Gi ``` ### Step-08-02: 02-mysql-deploy... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/26-GKE-PD-Volume-Snapshots-and-Restore/README.md | main | google-kubernetes-engine | [
-0.058278828859329224,
-0.04338710382580757,
0.02046266384422779,
-0.034844450652599335,
0.013281612657010555,
-0.014918089844286442,
0.009602644480764866,
-0.00907520018517971,
0.04074723646044731,
0.09333840012550354,
0.03504953533411026,
-0.07791963219642639,
0.08284720778465271,
0.0103... | -0.004273 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, REGION, PROJECT gcloud container clusters get-creden... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/57-GKE-Continuous-Integration/README.md | main | google-kubernetes-engine | [
-0.003284557955339551,
0.004490795079618692,
0.0522623285651207,
-0.06803476065397263,
-0.02589474804699421,
-0.043086133897304535,
-0.041661523282527924,
-0.08725827187299728,
-0.027666177600622177,
0.047736167907714844,
-0.011244688183069229,
-0.13906721770763397,
0.03991318494081497,
-0... | 0.034181 |
point to "id\_gcp\_cloud\_source" private key vi config ## Sample Output after changes Kalyans-Mac-mini:.ssh kalyanreddy$ cat config Host \* AddKeysToAgent yes UseKeychain yes IdentityFile ~/.ssh/id\_gcp\_cloud\_source Kalyans-Mac-mini:.ssh kalyanreddy$ # Backup config with cloudsource cp config config\_with\_cloud\_so... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/57-GKE-Continuous-Integration/README.md | main | google-kubernetes-engine | [
0.009279435500502586,
-0.011654685251414776,
-0.008591909892857075,
-0.030652405694127083,
-0.002890818752348423,
0.008465992286801338,
0.03800828754901886,
-0.0011085552396252751,
0.008363613858819008,
0.0963645726442337,
0.052451491355895996,
-0.049007318913936615,
0.025629626587033272,
... | -0.063726 |
Repositories https://source.cloud.google.com/repos Go to Repo -> myapp1-app-repo ``` ## Step-17: Create Continuous Integration Pipeline in Cloud Build - Go to Cloud Build -> Dashboard -> Region: us-central-1 -> Click on \*\*SET UP BUILD TRIGGERS\*\* [OR] - Go to Cloud Build -> TRIGGERS -> Click on \*\*CREATE TRIGGER\*\... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/57-GKE-Continuous-Integration/README.md | main | google-kubernetes-engine | [
-0.010618590749800205,
-0.07401654124259949,
0.03748498484492302,
-0.04752383381128311,
0.005741684231907129,
-0.03425563871860504,
-0.03963818773627281,
-0.022884231060743332,
0.0265450868755579,
0.09272866696119308,
0.008985480293631554,
-0.12023540586233139,
0.06320969760417938,
-0.0740... | -0.025063 |
Principal:\*\* dkalyanreddy@gmail.com - \*\*Assign Roles:\*\* Cloud Build Approver - Click on \*\*SAVE\*\* ## Step-27: Update the Git Repo to test Build Approval Process ```t # Change Directroy cd myapp1-app-repo # Update file index.html (change V2 to V3) Application Version: V3 # Local Git Commit and Push to Remote Re... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/57-GKE-Continuous-Integration/README.md | main | google-kubernetes-engine | [
-0.03301336616277695,
-0.062467873096466064,
0.10540875792503357,
-0.04403066262602806,
0.01023054402321577,
-0.03160065412521362,
-0.01894148252904415,
-0.05853266268968582,
0.041329532861709595,
0.11868291348218918,
0.033105019479990005,
-0.11817328631877899,
0.007362577132880688,
-0.060... | -0.050839 |
## Step-01: Introduction to ReplicaSets - What are ReplicaSets? - What is the advantage of using ReplicaSets? ## Step-02: Create ReplicaSet ### Step-02-01: Create ReplicaSet - Create ReplicaSet ```t # Kubernetes ReplicaSet kubectl create -f replicaset-demo.yml ``` - \*\*replicaset-demo.yml\*\* ```yaml apiVersion: apps/... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/07-kubectl-declarative-k8s-ReplicaSets/README.md | main | google-kubernetes-engine | [
-0.03430287912487984,
0.029532279819250107,
0.010153450071811676,
-0.020352909341454506,
0.029082614928483963,
-0.020290063694119453,
-0.01435755379498005,
-0.009160107001662254,
0.07264748215675354,
0.009867939166724682,
0.05594798922538757,
-0.10523698478937149,
0.008695616386830807,
-0.... | 0.186181 |
## Step-00: Introduction - Why do we need Pausing & Resuming Deployments? - If we want to make multiple changes to our Deployment, we can pause the deployment make all changes and resume it. - We are going to update our Application Version from \*\*V3 to V4\*\* as part of learning "Pause and Resume Deployments" ## Step... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/11-kubectl-imperative-k8s-deployment-PAUSE-RESUME/README.md | main | google-kubernetes-engine | [
-0.021847473457455635,
-0.03903919458389282,
0.05081988498568535,
-0.042357128113508224,
-0.0027450346387922764,
-0.0009744851267896593,
-0.041828423738479614,
-0.059785302728414536,
0.03154648467898369,
0.03749090060591698,
0.047037508338689804,
-0.02535177581012249,
-0.01864660158753395,
... | 0.135999 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, ZONE, PROJECT gcloud container clusters get-credenti... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/40-GKE-Ingress-Google-Managed-SSL-Redirect/README.md | main | google-kubernetes-engine | [
-0.016976458951830864,
-0.004296508617699146,
0.022789571434259415,
-0.04633063077926636,
-0.061014916747808456,
-0.05484708026051521,
-0.03642875701189041,
-0.07218576222658157,
0.036298781633377075,
-0.001098612672649324,
-0.012463940307497978,
-0.11484681814908981,
0.05580376833677292,
... | 0.0033 |
## Step-00: Pre-requisites 1. Verify if GKE Cluster is created 2. Verify if kubeconfig for kubectl is configured in your local terminal ```t # Configure kubeconfig for kubectl gcloud container clusters get-credentials --region --project # Replace Values CLUSTER-NAME, REGION, PROJECT gcloud container clusters get-creden... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/51-GKE-Ingress-ClientIP-Affinity/README.md | main | google-kubernetes-engine | [
-0.02794208936393261,
-0.027650054544210434,
0.0030201785266399384,
-0.05501239746809006,
-0.06296976655721664,
-0.011828405782580376,
-0.032301727682352066,
0.004076397977769375,
0.03541885316371918,
0.0726008266210556,
-0.004612086806446314,
-0.1352616846561432,
-0.0008505260339006782,
-... | 0.140317 |
enabled configuration, set the field's value to an empty string ("") or to a Boolean value of false, depending on the field type. ```yaml apiVersion: cloud.google.com/v1 kind: BackendConfig metadata: name: my-backendconfig spec: timeoutSec: 42 # Backend service timeout: https://cloud.google.com/kubernetes-engine/docs/h... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/51-GKE-Ingress-ClientIP-Affinity/README.md | main | google-kubernetes-engine | [
0.008721902966499329,
0.06636098027229309,
0.0464770570397377,
0.040731679648160934,
-0.019051557406783104,
0.001583106815814972,
-0.005159534513950348,
-0.051329635083675385,
0.07653231173753738,
0.05243668332695961,
-0.024527335539460182,
-0.04233792796730995,
0.0018033498199656606,
-0.0... | 0.06498 |
## Step-01: Kubernetes YAML Top level Objects - Discuss about the k8s YAML top level objects - \*\*kube-base-definition.yml\*\* ```yml apiVersion: kind: metadata: spec: ``` - [Kubernetes Reference](https://kubernetes.io/docs/reference/) - [Kubernetes API Reference](https://kubernetes.io/docs/reference/kubernetes-api/) ... | https://github.com/stacksimplify/google-kubernetes-engine/blob/main/14-yaml-declarative-k8s-pods/README.md | main | google-kubernetes-engine | [
0.008897196501493454,
0.036078084260225296,
0.06409145146608353,
-0.007314563263207674,
-0.0005875611095689237,
-0.00488573731854558,
0.005684647709131241,
0.012289182282984257,
0.015564829111099243,
0.02652888186275959,
-0.011108717881143093,
-0.08900302648544312,
-0.014785079285502434,
-... | 0.142589 |
# Adding a Consul Config Field This is a checklist of all the places you need to update when adding a new field to config. There may be a few other special cases not included but this covers the majority of configs. We suggest you copy the raw markdown into a gist or local file and check them off as you go (you can mar... | https://github.com/hashicorp/consul/blob/main/docs/config/checklist-adding-config-fields.md | main | consul | [
-0.008443697355687618,
0.007979190908372402,
-0.043762512505054474,
-0.059521693736314774,
0.014014596119523048,
-0.04163587838411331,
0.022387972101569176,
0.06682085245847702,
-0.02196459099650383,
0.08275281637907028,
0.047759853303432465,
-0.04809816554188728,
0.022193240001797676,
0.0... | 0.067477 |
Service Definition, make sure you continue on to follow the appropriate checklists below. ## Adding a CLI Flag Corresponding to the new Field If the config field also needs a CLI flag, then follow these steps. - [ ] Do all of the steps in [Adding a Simple Config Field For Client Agents](#adding-a-simple-config-field-fo... | https://github.com/hashicorp/consul/blob/main/docs/config/checklist-adding-config-fields.md | main | consul | [
0.028360553085803986,
-0.03164688125252724,
-0.10769310593605042,
-0.05583866313099861,
-0.06657000631093979,
-0.03853471204638481,
0.04617009311914444,
0.012340487912297249,
-0.1030358374118805,
0.0012974131386727095,
0.051671870052814484,
-0.030173659324645996,
0.07389311492443085,
0.073... | -0.001228 |
both config files and API bodies to avoid needless confusion, we have to accept both snake case and camel case field names for the service definition. Finally, adding a field to the service definition implies adding the field to several internal structs and to all API outputs that display services from the catalog. Tha... | https://github.com/hashicorp/consul/blob/main/docs/config/checklist-adding-config-fields.md | main | consul | [
-0.07105127722024918,
0.008092773146927357,
-0.03219262883067131,
-0.040194813162088394,
-0.0431474931538105,
-0.047578003257513046,
0.029434161260724068,
0.01578313298523426,
-0.08418554067611694,
-0.005329390987753868,
0.03262680023908615,
-0.014957964420318604,
0.058534275740385056,
0.0... | 0.071419 |
is needed, tests for these endpoints might be warranted too. It's usual to use `omit-empty` for new fields that will typically not be used by existing registrations although we don't currently test for that systematically. | https://github.com/hashicorp/consul/blob/main/docs/config/checklist-adding-config-fields.md | main | consul | [
-0.02142711728811264,
-0.04253562167286873,
-0.0169516708701849,
0.04435388743877411,
0.031570930033922195,
0.004674007650464773,
-0.0180978886783123,
-0.0740518793463707,
0.03780258074402809,
-0.08083053678274155,
0.07939426600933075,
-0.0609600804746151,
-0.02859639935195446,
-0.02274131... | 0.009838 |
# Adding a Changelog Entry Any change that a Consul user might need to know about should have a changelog entry. What doesn't need a changelog entry? - Docs changes - Typos fixes, unless they are in a public-facing API - Code changes we are certain no Consul users will need to know about To include a [changelog entry](... | https://github.com/hashicorp/consul/blob/main/docs/contributing/add-a-changelog-entry.md | main | consul | [
-0.03829921409487724,
0.046887267380952835,
-0.009658035822212696,
-0.03218673914670944,
0.06287004798650742,
-0.005161473993211985,
-0.015216326341032982,
0.08395189046859741,
0.009209990501403809,
0.09992069751024246,
0.07114274799823761,
-0.004700374323874712,
-0.004770652391016483,
-0.... | 0.095972 |
# Forking the Consul Repo Community members wishing to contribute code to Consul must fork the Consul project (`your-github-username/consul`). Branches pushed to that fork can then be submitted as pull requests to the upstream project (`hashicorp/consul`). To locally clone the repo so that you can pull the latest from ... | https://github.com/hashicorp/consul/blob/main/docs/contributing/fork-the-project.md | main | consul | [
-0.01912304200232029,
-0.07341647148132324,
-0.053278181701898575,
-0.0819721519947052,
-0.04626341536641121,
-0.07052189856767654,
-0.04680231958627701,
0.09356489777565002,
-0.0017741817282512784,
0.04996956139802933,
0.043617963790893555,
-0.02378283068537712,
-0.010175889357924461,
0.0... | -0.012264 |
# Glossary This page collects brief definitions of some of the technical terms used in the documentation for Vault. - [Audit Device](#audit-device) - [Auth Method](#auth-method) - [Barrier](#barrier) - [Client Token](#client-token) - [Plugin](#plugin) - [Request](#request) - [Secret](#secret) - [Secrets Engine](#secret... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/glossary.mdx | main | vault | [
-0.023865262046456337,
0.04318315535783768,
-0.08097125589847565,
-0.04070809856057167,
0.032016441226005554,
-0.0650472566485405,
0.05988619104027748,
-0.025712255388498306,
0.06478744000196457,
-0.02114681713283062,
0.0012356170918792486,
0.030224772170186043,
0.05002949759364128,
0.0113... | 0.128397 |
for further information on how [Namespaces can be specified](/vault/docs/enterprise/namespaces#vault-api-and-namespaces) as part of a request. #### Operation The request's operation can be one of the following: `alias-lookahead`, `create`, `delete`, `header`, `help`, `list`, `patch`, `read`, `renew`, `resolve-role`, `r... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/glossary.mdx | main | vault | [
-0.10599129647016525,
0.028712643310427666,
-0.05577635020017624,
0.041635386645793915,
-0.04344058036804199,
-0.037908293306827545,
-0.010743871331214905,
-0.024420902132987976,
0.06791052222251892,
-0.03635376691818237,
0.015065731480717659,
0.06895454227924347,
0.057075414806604385,
-0.... | 0.034029 |
# Manage custom messages in the Vault UI @include 'alerts/enterprise-only.mdx' Use custom banners and modals in the Vault UI to share system-wide alerts for all Vault UI users. 1. \*\*Messages are sticky\*\*. Users can only dismiss messages \*\*temporarily\*\*. The message reappears if the user refreshes their browser ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/custom-messages.mdx | main | vault | [
0.07177893072366714,
0.05618564784526825,
0.004372387658804655,
0.0003068168880417943,
0.0188436321914196,
-0.0844498872756958,
0.07423075288534164,
-0.030310094356536865,
0.06998554617166519,
-0.03391267731785774,
-0.0003405787283554673,
0.02959585003554821,
0.1098490059375763,
0.05884343... | 0.052814 |
new message. Your new message only appears when a user logs into the targeted namespace or one of its child namespaces. You can verify that your message has the correct behavior by logging into an admin or parent namespace. The message should only appear when you switch to the targeted namespace.  option in the Vault server configuration. The UI runs on the same port as the Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/index.mdx | main | vault | [
0.04772054776549339,
0.03335332125425339,
-0.05341806635260582,
-0.0785585269331932,
-0.04197118058800697,
-0.08500351756811142,
-0.05641968175768852,
-0.0461227186024189,
0.03213650733232498,
-0.08290950953960419,
-0.003792169503867626,
0.009406567551195621,
0.06627768278121948,
0.0216106... | -0.055004 |
# Manage custom login settings for the Vault GUI @include 'alerts/enterprise-and-hcp.mdx' Use can use the Vault CLI or API to customize a default and one or more back up login method for the Vault GUI login form. ## Before you start - \*\*You must have Vault Enterprise 1.20.0 or higher installed.\*\* - \*\*You must hav... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
0.08297882974147797,
0.03605697304010391,
-0.0821637511253357,
-0.08400208503007889,
-0.06922726333141327,
0.00459644291549921,
-0.002685536164790392,
0.0297293271869421,
0.005384184420108795,
-0.03700977563858032,
-0.024755127727985382,
-0.005530175287276506,
0.11532290279865265,
0.054485... | -0.081752 |
`listing\_visibility` parameter to `unauth`. For example: ```json { "description": "Default GUI auth method", "config": { "listing\_visibility": "unauth" } } ``` 1. Make a `POST` call to [`/sys/auth/{plugin\_mount\_path}`](/vault/api-docs/system/auth#enable-auth-method) with the JSON data: ```shell-session $ curl \ --r... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
-0.015611873008310795,
0.07384109497070312,
-0.12256666272878647,
0.011018174700438976,
0.0020079496316611767,
-0.05261518806219101,
-0.016549836844205856,
0.051306236535310745,
0.0062491195276379585,
-0.0030566544737666845,
0.05095751956105232,
-0.0585000216960907,
0.05115167424082756,
0.... | -0.051379 |
``` For example, to customize the login options for the `dev` namespace and set `userpass` as the default authentication method with `ldap` and `token` as additional, backup options: ```json { "namespace\_path": "dev", "default\_auth\_type": "userpass", "disable\_inheritance": false, "backup\_auth\_types": ["ldap", "to... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
-0.010231636464595795,
0.021296868100762367,
-0.08483753353357315,
0.0007556682685390115,
-0.08125567436218262,
-0.04227510094642639,
-0.02348712645471096,
0.07724384218454361,
-0.04188496246933937,
0.004767395090311766,
-0.004850730765610933,
-0.047286346554756165,
0.06138339266180992,
0.... | -0.075996 |
# Manage namespaces in the Vault GUI @include 'alerts/enterprise-only.mdx' Use namespaces in Vault Enterprise to create isolated environments within a single Vault cluster. You can use namespaces to organize teams, projects, or environments, and delegate management to different administrators. For guidance on structuri... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/namespaces.mdx | main | vault | [
0.05953887104988098,
-0.07714719325304031,
-0.08657261729240417,
-0.024561481550335884,
-0.027486082166433334,
-0.07564388960599899,
-0.0073561654426157475,
-0.02507045865058899,
0.052695974707603455,
-0.0073083690367639065,
-0.023190774023532867,
-0.046880658715963364,
0.13092133402824402,
... | -0.009198 |
# Vault GUI browser support Using the Vault GUI with an unsupported browser can degrade functionality for some features and render others nonfunctional. We strongly encourage using the latest version one of the following, supported browsers: - [Chrome](https://www.google.com/chrome) - [Firefox](https://www.mozilla.org/... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/ui/browser-support.mdx | main | vault | [
-0.07123596221208572,
-0.021347135305404663,
-0.059167154133319855,
-0.0266557764261961,
0.022545404732227325,
-0.09541329741477966,
-0.0744955763220787,
-0.02000194787979126,
0.028956998139619827,
-0.09604722261428833,
0.02872488833963871,
0.06938917934894562,
0.01465193834155798,
0.06224... | -0.037834 |
# Configure completed request logging Vault can be configured to log completed requests using the `log\_requests\_level` configuration parameter. ## Activating logging completed requests By default, logging completed requests is disabled. To activate request logging, set the `log\_requests\_level` configuration option ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/log-requests-level.mdx | main | vault | [
0.05395360291004181,
0.021881910040974617,
-0.056756649166345596,
-0.011669619008898735,
-0.017184920608997345,
-0.12235347926616669,
-0.015666792169213295,
-0.025525443255901337,
0.017168637365102768,
-0.0069796182215213776,
-0.02240675315260887,
-0.02141941525042057,
0.054247207939624786,
... | -0.055215 |
# Rate limit quotas - collective, by IP, by entity As the number of Vault client applications increases, the incoming requests to Vault can degrade Vault's performance. To protect your Vault environment's stability and network, as well as storage resource consumption, use [rate limit quotas](/vault/docs/configuration/c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/identity-based-rate-limit.mdx | main | vault | [
0.014215459115803242,
0.039543770253658295,
-0.05033828318119049,
-0.02424449473619461,
-0.03199584409594536,
-0.08233499526977539,
-0.044909603893756866,
-0.02379661239683628,
0.10655829310417175,
0.012226061895489693,
-0.026392508298158646,
0.014072109945118427,
0.09600792825222015,
0.02... | 0.01877 |
[Terraform Vault provider](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/quota\_rate\_limit) to configure and implement quotas instead of making API calls. - Define at least one lease count quota to protect your Vault cluster from [lease explosions](/vault/docs/configuration/prevent-leas... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/identity-based-rate-limit.mdx | main | vault | [
0.017960641533136368,
0.06575218588113785,
-0.012928348034620285,
-0.02829081565141678,
0.01320950873196125,
-0.10009191930294037,
-0.04289153963327408,
-0.017200909554958344,
0.05192552134394646,
0.0017902000108733773,
-0.015945281833410263,
-0.028873445466160774,
0.06920070201158524,
0.0... | 0.082937 |
# Prevent lease explosions As your Vault environment scales to meet deployment needs, you run the risk of lease explosions. Lease explosions can occur when a Vault cluster is over-subscribed and clients overwhelm system resources with consistent, high-volume API requests Unchecked lease explosions create a memory drain... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/prevent-lease-explosions.mdx | main | vault | [
0.06011548265814781,
0.01262736413627863,
0.002180008916184306,
0.016865024343132973,
0.003822796745225787,
-0.06491206586360931,
-0.045408714562654495,
-0.024589134380221367,
0.06702680885791779,
0.01379475835710764,
0.026270559057593346,
0.0611579455435276,
0.06363546848297119,
0.0202329... | 0.020497 |
Learn how to [query audit device logs](/vault/tutorials/monitoring/query-audit-device-logs). - Review [recommended Vault lease limits](/vault/docs/internals/limits#lease-limits). - Review [lease anti-patterns](/well-architected-framework/operational-excellence/security-vault-anti-patterns#not-adjusting-the-default-leas... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/prevent-lease-explosions.mdx | main | vault | [
0.09704069793224335,
0.03231055289506912,
-0.03914406895637512,
-0.023402253165841103,
0.006710889749228954,
-0.08813998103141785,
-0.03198530524969101,
-0.03608083724975586,
0.02392350696027279,
0.00714728282764554,
0.03943924605846405,
0.020177572965621948,
0.029032684862613678,
0.067640... | -0.017065 |
# `adaptive\_overload\_protection` stanza @include 'alerts/enterprise-only.mdx' As of Vault 1.18.0, adaptive overload protection is enabled by default Configure the `adaptive\_overload\_protection` stanza to control overload protection features for your Vault server. @include 'config-reload-supported.mdx' Do not disabl... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/adaptive-overload-protection.mdx | main | vault | [
0.03145549073815346,
0.05714399367570877,
-0.02816460095345974,
-0.018371209502220154,
0.008563225157558918,
-0.04461279883980751,
-0.028266312554478645,
-0.035831425338983536,
-0.009948919527232647,
-0.04059694707393646,
-0.005995703395456076,
0.07693812996149063,
0.11453831940889359,
-0.... | -0.033117 |
# Create a lease count quota Use lease count quotas to limit the number of leases generated on a per-mount basis and control resource consumption for your Vault instance where hard limits makes sense. ## Before you start - \*\*Confirm you have access to the root or administration namespace for your Vault instance\*\*. ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-lease-count-quota.mdx | main | vault | [
0.06562022864818573,
0.03517674654722214,
-0.06239312142133713,
-0.0023139326367527246,
-0.052041955292224884,
-0.031025493517518044,
0.0038481561932712793,
0.019051754847168922,
0.04102593660354614,
0.03919079899787903,
-0.0099562993273139,
-0.036829326301813126,
0.12009641528129578,
0.05... | -0.041495 |
# Vault configuration parameters Outside of development mode, Vault servers are configured using a file. The format of this file is [HCL](https://github.com/hashicorp/hcl) or JSON. @include 'plugin-file-permissions-check.mdx' An example configuration is shown below: For multi-node clusters, replace the loopback address... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
0.0582319013774395,
0.06183676794171333,
-0.11647748202085495,
-0.01266662310808897,
-0.007424511015415192,
-0.10237675905227661,
-0.07689278572797775,
-0.036094047129154205,
-0.008346159011125565,
-0.04910312220454216,
0.03158096596598625,
0.0119099710136652,
0.08365174382925034,
-0.00687... | -0.019003 |
use swap at all. Vault only supports memory locking on UNIX-like systems that support the mlock() syscall (Linux, FreeBSD, etc). Non UNIX-like systems (e.g. Windows, NaCL, Android) lack the primitives to keep a process's entire memory address space from spilling to disk and is therefore automatically disabled on unsupp... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.0016332893865182996,
-0.020722646266222,
-0.031281545758247375,
-0.01281894464045763,
-0.028951989486813545,
-0.011924286372959614,
-0.04580153897404671,
0.033179521560668945,
0.04197927936911583,
0.009228161536157131,
-0.028223857283592224,
0.13411906361579895,
0.011684060096740723,
-0... | -0.031892 |
cancels the request. This can be overridden per listener via the `max\_request\_duration` value. - `detect\_deadlocks` `(string: "")` - A comma separated string that specifies the internal mutex locks that should be monitored for potential deadlocks. Currently supported values include `statelock`, `quotas` and `expirat... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.05936064198613167,
0.019744738936424255,
-0.06855085492134094,
-0.02939850278198719,
0.018589407205581665,
-0.0540924146771431,
0.04333372041583061,
-0.028673944994807243,
0.08709237724542618,
0.04285048693418503,
0.02864326909184456,
0.021336903795599937,
-0.003524717641994357,
-0.0302... | 0.132747 |
counting by role if there are no role based quotas enabled. When `imprecise\_lease\_role\_tracking` is set to true and a new role-based quota is enabled, subsequent lease counts start from 0. `imprecise\_lease\_role\_tracking` affects role-based lease count quotas, but reduces latencies when not using role based quotas... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
0.011642820201814175,
-0.004481527954339981,
-0.08135325461626053,
0.03781462460756302,
-0.0027074378449469805,
-0.029453884810209274,
0.037867363542318344,
-0.016553444787859917,
0.057044871151447296,
-0.053304191678762436,
0.05403309315443039,
-0.018689727410674095,
0.06751829385757446,
... | 0.048043 |
leases. When the configured duration exceeds the expiry time of an irrevocable lease, Vault deletes the lease. The minimum value for `remove\_irrevocable\_lease\_after` is 2 days (`2d`). If you set the removal window to a value less than the minimum, Vault overwrites the value to `2d`. Deleting a lease may cause Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.0038601229898631573,
0.05057786405086517,
-0.04009915143251419,
0.03936944901943207,
-0.009577600285410881,
-0.0665016695857048,
-0.0436953566968441,
-0.026552021503448486,
0.10660791397094727,
0.007603909820318222,
0.07613047957420349,
0.09513875097036362,
0.006825835909694433,
0.01621... | -0.010312 |
# Manage Vault resources programmatically with Terraform Use Terraform to manage policies, namespaces, and plugins in Vault. ## Before you start - \*\*You must have [Terraform installed](/terraform/install)\*\*. - \*\*You must have the [Terraform Vault provider](https://registry.terraform.io/providers/hashicorp/vault/l... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/programmatic-management.mdx | main | vault | [
0.018897706642746925,
-0.04246021807193756,
-0.04571843519806862,
-0.03437473252415657,
-0.04754451662302017,
-0.05122414231300354,
-0.05556400120258331,
-0.054076556116342545,
0.008566935546696186,
0.040761448442935944,
-0.014186250045895576,
-0.08451095223426819,
0.07152599096298218,
0.0... | -0.052292 |
your existing, non-root policies to the file: ```shell-session for vpolicy in $(vault policy list | grep -vw root) ; do echo "resource \"vault\_policy\" \"vault\_$vpolicy\" {" echo " name = \"$vpolicy\"" echo " policy = < vault\_policies.tf ``` 1. Update the `vault\_policies.tf` file with any new policies you want to a... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/programmatic-management.mdx | main | vault | [
0.05547720938920975,
0.061494555324316025,
-0.10419806838035583,
-0.07983382791280746,
0.00022806857305113226,
-0.006539654452353716,
-0.015485187061131,
0.021968204528093338,
-0.02733953669667244,
-0.007770889438688755,
0.05355622246861458,
-0.030110670253634453,
0.09462600201368332,
-0.0... | -0.109859 |
# Configure entropy augmentation Entropy augmentation enables Vault to sample entropy from external cryptographic modules. Sourcing external entropy is done by configuring a supported [Seal](/vault/docs/configuration/seal) type which include: [PKCS11 seal](/vault/docs/configuration/seal/pkcs11), [AWS KMS](/vault/docs/c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/entropy-augmentation.mdx | main | vault | [
-0.018313074484467506,
0.044980488717556,
-0.044656191021203995,
-0.058773212134838104,
0.024760132655501366,
-0.04423467442393303,
-0.0028126463294029236,
-0.005074229557067156,
0.0875319316983223,
-0.022877860814332962,
0.008609520271420479,
-0.020570242777466774,
0.027879495173692703,
-... | 0.020506 |
# `reporting` stanza @include 'alerts/enterprise-only.mdx' The `reporting` stanza specifies various parameters for tuning replication related values. Please see the pages relating to [license utilization reporting](/vault/docs/enterprise/license/utilization-reporting) and [product usage reporting](/vault/docs/enterpris... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/reporting.mdx | main | vault | [
-0.005350665654987097,
0.0447847917675972,
-0.10831283032894135,
-0.061874810606241226,
-0.007034048903733492,
0.014400292187929153,
-0.007002305705100298,
-0.005165732000023127,
0.01806764304637909,
-0.051105763763189316,
0.002038906794041395,
0.050714410841464996,
0.11705193668603897,
-0... | 0.003517 |
# `telemetry` stanza The `telemetry` stanza specifies various configurations for Vault to publish metrics to upstream systems. Available Vault metrics can be found in the [Telemetry internals documentation](/vault/docs/internals/telemetry). ```hcl telemetry { statsite\_address = "statsite.company.local:8125" } ``` Metr... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.03781546279788017,
0.02916000969707966,
-0.07043176144361496,
0.014217264950275421,
-0.022314157336950302,
-0.04986916482448578,
0.04251649230718613,
0.014439529739320278,
0.05346587300300598,
-0.045800693333148956,
0.03569598123431206,
-0.040283411741256714,
0.046443626284599304,
-0.03... | 0.067952 |
`false` with no filters, no metrics will be sent. - `prefix\_filter` `(string array: [])` - This is a list of filter rules to apply for allowing/blocking metrics by prefix in the following format: ```json ["+vault.token", "-vault.expire", "+vault.expire.num\_leases"] ``` A leading "\*\*+\*\*" will enable any metrics wi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.09214483201503754,
0.0644342377781868,
-0.06919080764055252,
-0.045034151524305344,
-0.05283873528242111,
-0.10041496157646179,
0.02170594222843647,
-0.06035730987787247,
0.05047710984945297,
-0.04418705403804779,
0.051899414509534836,
-0.034413643181324005,
0.039114873856306076,
0.0129... | 0.059227 |
- `circonus\_broker\_select\_tag` `(string: "")` - Specifies a special tag which will be used to select a Circonus Broker when a Broker ID is not provided. The best use of this is to as a hint for which broker should be used based on \_where\_ this particular instance is running (e.g. a specific geo location or datacen... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.02688385732471943,
0.03188660740852356,
-0.08947198837995529,
-0.010829371400177479,
-0.07483652979135513,
-0.0753350779414177,
0.03479069098830223,
0.007299258839339018,
0.03479297459125519,
-0.02909131534397602,
0.08256962895393372,
-0.04611716791987419,
0.07264672219753265,
-0.050079... | 0.109971 |
option `disable\_hostname` to avoid having prefixed metrics with hostname and enable instead `enable\_hostname\_label`. ```hcl telemetry { stackdriver\_project\_id = "my-test-project" stackdriver\_location = "us-east1-a" stackdriver\_namespace = "vault-cluster-a" disable\_hostname = true enable\_hostname\_label = true ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
0.021441075950860977,
-0.0020431929733604193,
-0.04620515927672386,
0.0006146475207060575,
-0.09280321002006531,
-0.08797341585159302,
-0.006869607605040073,
-0.0663195475935936,
0.06872949749231339,
-0.06448927521705627,
-0.002712228102609515,
-0.09904929250478745,
0.07334352284669876,
0.... | -0.029898 |
# `kms\_library` stanza The `kms\_library` stanza isolates platform specific configuration for managed keys. It defines logical names that are referenced within an API configuration keeping cluster and node specific details separated along with deployment concerns for each. At the moment managed keys are only available... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/kms-library.mdx | main | vault | [
0.029952822253108025,
-0.009159587323665619,
-0.06233848258852959,
-0.025673164054751396,
-0.003311904612928629,
0.004533294588327408,
-0.010967778041958809,
0.0031645020935684443,
-0.0042692930437624454,
-0.016195407137274742,
0.012918048538267612,
-0.006363046355545521,
0.10081566125154495... | -0.044214 |
# Create a rate limit quota Vault's rate limit quotas allow Vault admins to control how traffic enters the Vault cluster by setting a limit on the target namespace, mount, path, or role. It is a part of Vault's core feature set available in both Community and Enterprise Editions. The default behavior of rate limit quot... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.05283866450190544,
0.02414560317993164,
-0.06088511645793915,
-0.026955660432577133,
-0.021909769624471664,
-0.05767678841948509,
-0.03441347926855087,
-0.01752243936061859,
0.07880014181137085,
0.016510581597685814,
-0.01703115925192833,
-0.0007691740756854415,
0.07907666265964508,
0.04... | -0.028103 |
requests. Refer to the [identity-based rate limit quotas](/vault/docs/configuration/identity-based-rate-limit) for more details. - `secondary\_rate` `(float: 0.0)` – Can only be set for the `group\_by` modes `entity\_then\_ip` or `entity\_then\_none`. This is the rate limit applied to the requests that fall under the "... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.0094365319237113,
0.04009907692670822,
-0.08217041939496994,
-0.014381512999534607,
-0.05825721099972725,
-0.06994182616472244,
-0.0024060618598014116,
-0.029050830751657486,
0.11461034417152405,
0.04543719440698624,
0.023635275661945343,
-0.05140990391373634,
0.09096704423427582,
0.0106... | -0.01011 |
inheritably by setting the `inheritable` parameter to `true`. By default, it is set to `false`. 1. Create a quota rule on the `us-west` namespace which its child namespaces will inherit. The rate limit is 500 requests per minute. ```shell-session $ vault write sys/quotas/rate-limit/us-west \ path="us-west" \ rate=500 \... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.016778789460659027,
0.06106724590063095,
-0.08004773408174515,
-0.019187333062291145,
-0.09519747644662857,
-0.0876707062125206,
-0.0019981099758297205,
0.023972079157829285,
0.02340131811797619,
0.050611600279808044,
-0.023434115573763847,
-0.06155097857117653,
0.07622362673282623,
-0.0... | 0.039035 |
applied to its child namespaces inheritably by setting the `inheritable` parameter to `true`. By default, it is set to `false`. 1. Create a quota rule on the `us-west` namespace which its child namespace inherits. The rate limit is 500 requests per minute. ```shell-session $ curl --header "X-Vault-Token: $VAULT\_TOKEN"... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.008406303822994232,
0.06850894540548325,
-0.07854478806257248,
-0.0052254702895879745,
-0.04528937488794327,
-0.08389075845479965,
-0.04696280509233475,
-0.015486280433833599,
0.08732763677835464,
0.02220851369202137,
0.014059695415198803,
-0.06769710034132004,
0.0513586699962616,
0.0033... | -0.024523 |
└── parent └── child └── grand-child ``` Under the `root` namespace, you have a `parent` namespace, and then `parent/child` and `parent/child/grand-child` namespaces. You can set the resource quota on the `parent` namespace which gets applied to its child namespaces inheritably by setting the `inheritable` parameter to... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
-0.021922517567873,
0.013291507959365845,
-0.026718679815530777,
-0.0060752336867153645,
-0.05087820068001747,
-0.09081543982028961,
-0.01529412530362606,
-0.05275540426373482,
0.044657934457063675,
0.05332913249731064,
-0.02272237092256546,
-0.10295838117599487,
0.10753782838582993,
0.011... | -0.030378 |
# Vault GUI configuration Vault features a user interface (web interface) for interacting with Vault. Easily create, read, update, and delete secrets, authenticate, unseal, and more with the Vault GUI. ## Activating the Vault GUI The Vault GUI is not activated by default. To activate the UI, set the `ui` configuration ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/ui.mdx | main | vault | [
0.02943335846066475,
0.06233282759785652,
-0.06348975002765656,
-0.03828999400138855,
-0.0744810625910759,
-0.03158342465758324,
-0.020300885662436485,
-0.015994779765605927,
0.033977389335632324,
-0.1064913272857666,
-0.017919443547725677,
-0.03394866734743118,
0.10026779025793076,
0.0121... | -0.075758 |
## CLI emulation in the Vault GUI The Vault GUI includes an interactive Web REPL to interact with Vault's API much like the Vault CLI. For more on that, see the [Web REPL documentation](/vault/docs/commands/web). | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/ui.mdx | main | vault | [
-0.024710051715373993,
-0.00008089302718872204,
-0.085415780544281,
-0.06857939064502716,
-0.0021297908388078213,
-0.07792704552412033,
-0.015150637365877628,
0.0027639265172183514,
0.04871037229895592,
-0.07811383157968521,
0.02246944047510624,
-0.008513863198459148,
0.08616872876882553,
... | 0.046994 |
# Best practices for programmatic Vault management It can be a challenge to enforce appropriate governance policies on resources created directly from the Vault CLI or API. The best way to manage Vault at scale is to [codify resource management](/vault/tutorials/operations/codify-mgmt-vault-terraform) with [Terraform](... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/programmatic-best-practices.mdx | main | vault | [
-0.011991173960268497,
0.03186320513486862,
-0.05410736799240112,
-0.003710889257490635,
-0.01179052609950304,
-0.05888250097632408,
-0.03231543302536011,
-0.03545102849602699,
0.014629954472184181,
0.05965316295623779,
-0.011079696007072926,
-0.02437603659927845,
0.06931296736001968,
0.02... | 0.035009 |
# `sentinel` stanza The sentinel stanza specifies configurations for [Vault's Sentinel](/vault/docs/enterprise/sentinel) integration. ```hcl sentinel { additional\_enabled\_modules = ["http"] } ``` ## Requirements A valid Vault Enterprise license is required for use of Sentinel policies. ## `sentinel` parameters The se... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/sentinel.mdx | main | vault | [
-0.014911076053977013,
-0.04459461569786072,
-0.0745411142706871,
0.0005832649185322225,
0.024792181327939034,
-0.04375647380948067,
-0.04614683613181114,
-0.0011500556720420718,
-0.02514147199690342,
-0.04973187670111656,
0.03711269050836563,
0.02291623316705227,
0.02562699094414711,
0.02... | 0.128476 |
# User lockout @include 'user-lockout.mdx' ## `user\_lockout` stanza The `user\_lockout` stanza specifies various configurations for user lockout behaviour for failed logins in vault. They can be configured for all supported auth methods (userpass, ldap and approle) using "all" user\_lockout stanza name or for a specif... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/user-lockout.mdx | main | vault | [
0.030426092445850372,
0.0339098758995533,
-0.07269202172756195,
-0.08103005588054657,
-0.043861024081707,
0.05009986087679863,
0.047063447535037994,
-0.0316699855029583,
0.012210729531943798,
-0.06327623873949051,
0.00602179067209363,
0.012011383660137653,
0.11800964176654816,
-0.035606160... | -0.022947 |
# `replication` stanza @include 'alerts/enterprise-only.mdx' The `replication` stanza specifies various parameters for tuning replication related values. ```hcl replication { resolver\_discover\_servers = true logshipper\_buffer\_length = 1000 logshipper\_buffer\_size = "5gb" allow\_forwarding\_via\_header = false best... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/replication.mdx | main | vault | [
0.027811303734779358,
-0.019720183685421944,
-0.003167880466207862,
0.019893663004040718,
0.019345775246620178,
-0.059568390250205994,
-0.01421947218477726,
-0.07457607239484787,
-0.01877947337925434,
0.04685792326927185,
-0.04195335507392883,
0.056110624223947525,
0.08535664528608322,
-0.... | 0.043987 |
# `service\_registration` stanza The optional `service\_registration` stanza configures Vault's mechanism for service registration. The `service\_registration` stanza is designed for use cases where you would like to use a system like [Consul][consul] for [service discovery][consul-discovery], but use a different syste... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/service-registration/index.mdx | main | vault | [
-0.05812311917543411,
-0.021956032142043114,
-0.07800236344337463,
-0.026908332481980324,
-0.05602024868130684,
-0.06243481487035751,
0.03059390000998974,
0.025736631825566292,
0.05087931081652641,
-0.06591092050075531,
0.026591312140226364,
0.003549599088728428,
0.0748240277171135,
0.0229... | -0.011254 |
# Configure Kubernetes service registration Kubernetes Service Registration tags Vault pods with their current status for use with selectors. Service registration is only available when Vault is running in [High Availability mode](/vault/docs/concepts/ha). - \*\*HashiCorp Supported\*\* – Kubernetes Service Registration... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/service-registration/kubernetes.mdx | main | vault | [
0.02659476548433304,
-0.023034904152154922,
0.003937062807381153,
-0.03366535156965256,
-0.05264073610305786,
-0.01381799578666687,
0.035960689187049866,
-0.00047097206697799265,
0.047202788293361664,
-0.024934496730566025,
0.006604693830013275,
-0.08853239566087723,
0.048525527119636536,
... | 0.053336 |
will always reach the active node. When setting up Vault replication, it can be used as the primary address: ```shell-session $ vault write -f sys/replication/performance/primary/enable \ primary\_cluster\_addr='https://vault-active-us-east:8201' ``` ### Example upgrades In conjunction with the pod labels and the `OnDe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/service-registration/kubernetes.mdx | main | vault | [
0.06473488360643387,
0.00510204816237092,
-0.009762274101376534,
-0.0003775805816985667,
0.02756202034652233,
-0.03687169775366783,
-0.04407820478081703,
-0.08102715015411377,
0.0868649110198021,
0.04505341872572899,
0.02278134413063526,
0.022670987993478775,
0.061757054179906845,
-0.05671... | 0.08452 |
# Configure Consul service registration Consul Service Registration registers Vault as a service in [Consul][consul] with a default health check. When Consul is configured as the storage backend, the stanza `service\_registration` is not needed as it will automatically register Vault as a service. ~> \*\*Version inform... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/service-registration/consul.mdx | main | vault | [
0.016596633940935135,
0.005621016025543213,
-0.08050315827131271,
-0.07004525512456894,
-0.05013389140367508,
-0.047093138098716736,
-0.05822043865919113,
0.025693682953715324,
0.03497995436191559,
-0.031112072989344597,
0.037854962050914764,
0.0013785905903205276,
0.05179879441857338,
0.0... | -0.042381 |
- `tls\_key\_file` `(string: "")` – Specifies the path to the private key for Consul communication. This should be set according to the [`key\_file`](/consul/docs/agent/config/config-files#key\_file) setting in Consul. - `tls\_min\_version` `(string: "tls12")` – Specifies the minimum TLS version to use. Accepted values... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/service-registration/consul.mdx | main | vault | [
-0.02642488107085228,
0.06038400158286095,
-0.11217403411865234,
-0.06655445694923401,
-0.04060027375817299,
-0.06918976455926895,
-0.036895543336868286,
0.049284663051366806,
0.06538191437721252,
0.03134752810001373,
0.03422768786549568,
0.019892431795597076,
0.05193187668919563,
0.085865... | -0.027128 |
# Unix listener configuration The Unix listener configures Vault to listen on the specified Unix domain socket. ```hcl listener "unix" { address = "/run/vault.sock" } ``` The `listener` stanza may be specified more than once to make Vault listen on multiple sockets. ## `unix` listener parameters - `address` `(string: "... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/unix.mdx | main | vault | [
0.026009175926446915,
-0.039074625819921494,
-0.12333937734365463,
-0.05912921205163002,
-0.06909554451704025,
-0.06883317977190018,
0.002954215044155717,
-0.024613266810774803,
0.06472719460725784,
-0.06551828980445862,
-0.014675363898277283,
0.039281945675611496,
0.08616958558559418,
-0.... | 0.018644 |
# TCP listener configuration @include 'alerts/ipv6-compliance.mdx' The TCP listener configures Vault to listen on a TCP address/port. ```hcl listener "tcp" { address = "127.0.0.1:8200" } ``` The `listener` stanza may be specified more than once to make Vault listen on multiple interfaces. If you configure multiple list... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.030847907066345215,
0.04129592329263687,
-0.05912288650870323,
-0.03599588945508003,
-0.021437954157590866,
-0.05052659660577774,
-0.016251537948846817,
-0.08030369132757187,
0.03309942036867142,
-0.08410768955945969,
-0.03281055763363838,
-0.01092996820807457,
0.11227881908416748,
-0.01... | 0.016221 |
to the Vault process. If a header is defined in the configuration file and the same header is used by the internal processes of Vault, the configured header is not accepted. For example, a custom header which has the `X-Vault-` prefix will not be accepted. A message will be logged in the Vault's logs upon start up indi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.016935832798480988,
0.08846042305231094,
-0.06184414401650429,
-0.04884708672761917,
0.022439725697040558,
-0.08304256945848465,
-0.018995940685272217,
0.010761690326035023,
0.07065674662590027,
-0.0264739952981472,
0.024899378418922424,
-0.01053489837795496,
0.08469170331954956,
0.05412... | -0.061248 |
specified, enables a PROXY protocol behavior for the listener (version 1 and 2 are both supported). Accepted Values: - \_use\_always\_ - The client's IP address will always be used. - \_allow\_authorized\_ - If the source IP address is in the `proxy\_protocol\_authorized\_addrs` list, the client's IP address will be us... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.07511527091264725,
0.016101906076073647,
-0.01758570410311222,
-0.06814295798540115,
-0.017458703368902206,
-0.027603961527347565,
0.10056792944669724,
-0.07217590510845184,
-0.050833024084568024,
-0.003491257783025503,
0.01585470326244831,
0.0018721242668107152,
0.036397844552993774,
-... | 0.051727 |
post][go-tls-blog]. - `tls\_prefer\_server\_cipher\_suites` `(string: "false")` – Specifies to prefer the server's ciphersuite over the client ciphersuites. ~> \*\*Warning\*\*: The `tls\_prefer\_server\_cipher\_suites` parameter is deprecated. Setting it has no effect. See the above [Go blog post][go-tls-blog] for more... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.0460059717297554,
0.08412587642669678,
-0.017151150852441788,
-0.022402862086892128,
-0.02897672913968563,
-0.04793436452746391,
-0.0024151932448148727,
-0.048793528228998184,
0.08283785730600357,
-0.03485516086220741,
0.04931119829416275,
0.03155790641903877,
0.046173345297575,
0.10544... | -0.0591 |
range of use cases. The primary constraints on parsing limits are available RAM and CPU. We recommend tuning your JSON parsing limits down from the defaults to match your specific application needs and available resourcess. Due to the way the parsing limits interact, running with permissive defaults in a low-resource e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.04581805691123009,
0.029611850157380104,
-0.018575862050056458,
-0.04984840750694275,
-0.05692698806524277,
-0.08651188760995865,
-0.09637178480625153,
0.09918943792581558,
-0.03874925151467323,
-0.061918601393699646,
-0.000827662879601121,
0.02634434774518013,
-0.036365609616041183,
0.... | 0.163674 |
"tcp" { address = "10.0.0.5:8200" } # Advertise the non-loopback interface api\_addr = "https://10.0.0.5:8200" cluster\_addr = "https://10.0.0.5:8201" ``` ### Configuring unauthenticated metrics access This example shows enabling unauthenticated metrics access. ```hcl listener "tcp" { telemetry { unauthenticated\_metri... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.03209865838289261,
0.05737840011715889,
-0.08623365312814713,
0.0002169426588807255,
-0.04697224870324135,
-0.043177831918001175,
0.037208884954452515,
-0.020961549133062363,
-0.018317092210054398,
-0.06506765633821487,
0.0068515571765601635,
-0.09010101109743118,
0.014451220631599426,
... | 0.076615 |
the empty string (`""`). ```shell-session $ curl -s https://127.0.0.1:8200/v1/sys/leader | jq`: { "ha\_enabled": true, "is\_self": false, "active\_time": "0001-01-01T00:00:00Z", "leader\_address": "", "leader\_cluster\_address": "", "performance\_standby": false, "performance\_standby\_last\_remote\_wal": 0, "raft\_com... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.007730503566563129,
0.09243987500667572,
-0.031068049371242523,
0.049571238458156586,
0.007623335346579552,
-0.036094531416893005,
0.003158936044201255,
-0.004710685927420855,
0.07354097068309784,
0.029801782220602036,
0.04940853640437126,
-0.04261910542845726,
-0.01590455323457718,
-0.0... | 0.10659 |
# Configure TLS for your Vault TCP listener You can configure your TCP listener to use specific versions of TLS and specific ciphersuites. ## Assumptions - \*\*Your Vault instance is not currently running\*\*. If your Vault cluster is running, you must [restart the cluster gracefully](https://support.hashicorp.com/hc/e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/tcp-tls.mdx | main | vault | [
0.02572096511721611,
0.09567283093929291,
-0.05080467835068703,
-0.039730288088321686,
-0.05935975909233093,
-0.05986936762928963,
-0.04426915571093559,
-0.09500715881586075,
0.09855443239212036,
-0.042961347848176956,
-0.01972632296383381,
-0.010749632492661476,
0.06467457860708237,
0.058... | -0.065138 |
Jun 16 17:27:29 2024 GMT ``` ```shell-session sslscan 127.0.0.1:8200 Testing SSL server 127.0.0.1 on port 8200 using SNI name 127.0.0.1 SSL/TLS Protocols: SSLv2 disabled SSLv3 disabled TLSv1.0 disabled TLSv1.1 disabled TLSv1.2 enabled TLSv1.3 enabled Supported Server Cipher(s): Preferred TLSv1.3 128 bits TLS\_AES\_128\... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/listener/tcp/tcp-tls.mdx | main | vault | [
-0.02160682901740074,
0.04955637454986572,
-0.01149672456085682,
-0.05653521791100502,
-0.006894958671182394,
-0.06312467902898788,
-0.08993086218833923,
-0.05383281037211418,
0.014467752538621426,
-0.013610700145363808,
-0.03848320245742798,
0.011209607124328613,
0.054925624281167984,
0.0... | -0.04568 |
# HSM PKCS11 seal configuration Auto-unseal \*\*and\*\* seal wrapping for PKCS11 require Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vault/docs/enterprise/sealwrap) overvie... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
-0.021711446344852448,
0.07144170254468918,
-0.051441583782434464,
-0.046088092029094696,
-0.02047378569841385,
-0.01055874302983284,
-0.06764049082994461,
-0.0018079286674037576,
-0.0265251062810421,
-0.060622796416282654,
-0.018289482221007347,
-0.031969621777534485,
0.016783244907855988,
... | -0.056771 |
The PIN for login. May also be specified by the `VAULT\_HSM\_PIN` environment variable. \_If set via the environment variable, it will need to be re-set if Vault is restarted.\_ - `key\_label` `(string: )`: The label of the key to use. If the key does not exist and generation is enabled, this is the label that will be ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
0.019291263073682785,
0.006980872713029385,
-0.09116773307323456,
-0.02532137557864189,
-0.005535396747291088,
0.006318764295428991,
0.023848757147789,
-0.002282863948494196,
0.024110127240419388,
-0.08382820338010788,
0.08678536862134933,
0.01582108624279499,
0.0421769954264164,
0.0131379... | -0.050532 |
has occurred post cluster initialization, it is advisable to disable this flag to prevent any unintended key creation in the future. - `force\_rw\_session` `(string: "false")`: Force all operations to open up a read-write session to the HSM. This is a boolean expressed as a string (e.g. `"true"`). May also be specified... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
0.010972626507282257,
0.025288695469498634,
-0.06864384561777115,
0.02081952430307865,
0.006673204712569714,
0.0014257647562772036,
-0.03610968589782715,
-0.053435612469911575,
0.015028933063149452,
0.037485551089048386,
0.03245283290743828,
0.004540190100669861,
0.04338419437408447,
-0.05... | -0.060161 |
be used for decryption) - `CKA\_UNWRAP`: `true` (Key can be used for unwrapping) - `CKA\_TOKEN`: `true` (Key persists to the slot/token rather than being for one session only) - `CKA\_EXTRACTABLE`: `false` (Key cannot be exported) ### HMAC key - `CKA\_CLASS`: `CKO\_SECRET\_KEY` (It's a secret key) - `CKA\_KEY\_TYPE`: `... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
-0.06063961237668991,
0.052827347069978714,
-0.056782227009534836,
-0.03401210904121399,
-0.05237428843975067,
0.006144052371382713,
0.02873484417796135,
0.01809934712946415,
0.03447206690907478,
0.004333398770540953,
0.02713899500668049,
-0.03712794929742813,
0.03846263140439987,
-0.01963... | 0.01073 |
# GCP Cloud KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for GCP Cloud, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wra... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/gcpckms.mdx | main | vault | [
0.029614461585879326,
0.03446095064282417,
0.04886431246995926,
-0.03495578467845917,
-0.044739626348018646,
-0.023747658357024193,
0.019563887268304825,
-0.029528072103857994,
0.002185753546655178,
0.0009675213950686157,
-0.004511355888098478,
-0.02655891329050064,
0.046880170702934265,
0... | -0.031004 |
the primary key version. ## Tutorial Refer to the [Auto-unseal using GCP Cloud KMS](/vault/tutorials/auto-unseal/autounseal-gcp-kms) guide for a step-by-step tutorial. | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/gcpckms.mdx | main | vault | [
-0.018333913758397102,
-0.0017206190386787057,
0.05682714655995369,
-0.05147380381822586,
-0.009952244348824024,
0.003218343248590827,
-0.017145531252026558,
-0.07634814828634262,
-0.03567852824926376,
0.007740985602140427,
-0.00134040298871696,
0.016923420131206512,
0.05004924163222313,
-... | 0.047653 |
# Auto-unseal best practices for the Transit plugin This document provides a framework for creating a usable solution for auto-unseal using Vault when HSM or cloud-based KMS auto-unseal mechanism is not available for your environment, such as in an internal data center deployment. ## Glossary - \*\*Region\*\*: A networ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/transit-best-practices.mdx | main | vault | [
0.002218099543824792,
-0.03113570623099804,
-0.0069619398564100266,
0.022187991067767143,
-0.02252938225865364,
-0.018742157146334648,
-0.0730876699090004,
-0.049020346254110336,
-0.020017625764012337,
-0.006346658803522587,
0.0008545549935661256,
0.005180048290640116,
0.06270409375429153,
... | 0.156532 |
material. You can deploy the unsealing Vault cluster on a small virtual machine or container. To minimize the resource, it can run as a single-node cluster. For simplicity, using a non-HA supporting backend, such as a [filesystem storage backend](/vault/docs/configuration/storage/filesystem), is a common practice. ## P... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/transit-best-practices.mdx | main | vault | [
0.03461167588829994,
0.023069282993674278,
-0.042117223143577576,
0.036398984491825104,
-0.009872774593532085,
-0.015308146364986897,
-0.09167428314685822,
0.0063255359418690205,
-0.009279544465243816,
-0.05363130196928978,
-0.0296795517206192,
-0.02053782343864441,
0.1062435507774353,
-0.... | 0.000446 |
# `seal` stanza The `seal` stanza configures the seal type to use for additional data protection, such as using HSM or Cloud KMS solutions to encrypt and decrypt the root key. This stanza is optional, and in the case of the root key, Vault will use the Shamir algorithm to cryptographically split the root key if this is... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/index.mdx | main | vault | [
0.02277611941099167,
0.05584424361586571,
-0.05160444974899292,
-0.05859784409403801,
-0.014870254322886467,
-0.044520679861307144,
-0.02017020806670189,
0.06300445646047592,
-0.007211979012936354,
-0.03173276409506798,
0.02019442990422249,
0.010042322799563408,
0.08324022591114044,
-0.024... | -0.055752 |
# Transit seal configuration All Vault versions support \*\*auto-unseal\*\* for Transit, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vaul... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/transit.mdx | main | vault | [
0.02140001580119133,
0.036544069647789,
0.022094186395406723,
0.006936412304639816,
-0.05859516188502312,
-0.01868620328605175,
-0.031200705096125603,
-0.04075445979833603,
0.01459153275936842,
-0.06902629137039185,
-0.022683236747980118,
-0.03393150120973587,
0.043980661779642105,
0.00808... | 0.008403 |
values must be provided, either as environment variables or as configuration parameters. ~> \*\*Note:\*\* Although the configuration file allows you to pass in `VAULT\_TOKEN` as part of the seal's parameters, it is \_strongly\_ recommended to set these values via environment variables. The Vault token used to authentic... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/transit.mdx | main | vault | [
-0.01214801799505949,
0.016273362562060356,
-0.02812868356704712,
-0.036143530160188675,
-0.0392707884311676,
-0.03716304898262024,
-0.007802185136824846,
0.044222909957170486,
0.017810489982366562,
-0.05884043127298355,
0.04029103368520737,
-0.01685134880244732,
0.08554520457983017,
0.009... | -0.018471 |
# AliCloud KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for AliCloud, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap]... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/configuration/seal/alicloudkms.mdx | main | vault | [
0.015069933608174324,
0.05747523158788681,
-0.0042375982739031315,
-0.024957867339253426,
-0.013188374228775501,
-0.038128580898046494,
0.024172158911824226,
-0.040303025394678116,
0.026881271973252296,
-0.027114873751997948,
0.009871067479252815,
-0.029610153287649155,
0.05380389094352722,
... | 0.001708 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.