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 |
|---|---|---|---|---|---|
# Set up SAML authentication @include 'alerts/enterprise-and-hcp.mdx' @include 'tips/custom-authn.mdx' The `saml` auth method allows users to authentication with Vault using their identity within a [SAML V2.0](https://saml.xml.org/saml-specifications) identity provider. Authentication is suited for human users by requi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/index.mdx | main | vault | [
0.006431872025132179,
0.035558346658945084,
-0.06050742417573929,
-0.05557171627879143,
-0.04990899935364723,
0.0037523899227380753,
0.06611432880163193,
-0.018690722063183784,
0.09408364444971085,
-0.06727632880210876,
0.010607738979160786,
-0.015599259175360203,
0.07670160382986069,
0.06... | -0.070784 |
to TLS-protect the assertion consumer service URLs. A warning will be returned from Vault if any of the configured assertion consumer service URLs are not protected by TLS. #### Configuration for replication To support a single auth method mount being used across Vault [replication](/vault/docs/enterprise/replication) ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/index.mdx | main | vault | [
-0.07814822345972061,
0.0456121526658535,
-0.08774803578853607,
-0.04011248052120209,
0.008923547342419624,
-0.05053478851914406,
0.0025875286664813757,
-0.05334446206688881,
0.08704007416963577,
-0.022710731253027916,
0.02498820051550865,
-0.035185012966394424,
0.12201453000307083,
0.0496... | -0.009226 |
# Link Active Directory SAML groups to Vault @include 'alerts/enterprise-and-hcp.mdx' Configure your Vault instance to link your Active Directory groups to Vault policies with SAML. ## Before you start - \*\*You must have Vault Enterprise or HCP Vault v1.15.5+\*\*. - \*\*You must be running AD FS on Windows Server\*\*.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/link-vault-group-to-ad.mdx | main | vault | [
0.013752502389252186,
-0.015052038244903088,
-0.0990258976817131,
-0.006917632184922695,
-0.009413630701601505,
-0.0006561868358403444,
0.030736684799194336,
-0.025927888229489326,
0.03421584889292717,
-0.032014984637498856,
0.03547937050461769,
-0.042800258845090866,
0.07640518993139267,
... | -0.07109 |
# Troubleshoot AD FS: Before you start Troubleshooting guidance for solving problems with AD FS and SAML. ## Temporarily enable verbose logging Expanding SAML response data is a \*\*temporary\*\* change. Do not leave verbose logging on in production as SAML responses may contain sensitive information. 1. Enable verbose... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/index.mdx | main | vault | [
0.028858931735157967,
-0.009364169090986252,
-0.07040374726057053,
0.05316818878054619,
-0.0014370062854140997,
-0.061051737517118454,
0.012438944540917873,
-0.04873717203736305,
0.03299759700894356,
0.04389948397874832,
0.04355594143271446,
-0.017910227179527283,
0.017712535336613655,
0.0... | -0.086075 |
# AD FS event 320 Troubleshoot problems where your AD FS event logs show error 320. ## Example debugging data AD FS event log shows the following error: ```shell-session The verification of the SAML message signature failed. Message issuer: MyVaultIdentifier Exception details: MSIS7086: The relying party trust 'MyVault... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/adfs-event-320.mdx | main | vault | [
0.008911197073757648,
-0.008143983781337738,
-0.06293244659900665,
-0.011128505691885948,
0.003159720916301012,
-0.06971708685159683,
0.06442536413669586,
-0.01784648187458515,
0.005120857618749142,
0.07499178498983383,
0.03312068432569504,
-0.049433086067438126,
0.06042037531733513,
0.082... | -0.087176 |
# Clients cannot connect to Vault: invalid `BoundSubjects` Troubleshoot problems where the debugging data suggests a problem with bound subjects. ## Example debugging data ```json [DEBUG] auth.saml.auth\_saml\_b1886dfe: validating user context for role: api=callback role\_name=default-saml role="{ "token\_bound\_cidrs"... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/boundsubjects.mdx | main | vault | [
-0.018536647781729698,
0.029656346887350082,
-0.08074184507131577,
-0.018193069845438004,
-0.07254654914140701,
-0.07851266860961914,
-0.0043005128391087055,
-0.0013332297094166279,
0.021357132121920586,
-0.002940775826573372,
0.008183878846466541,
-0.010468351654708385,
0.04871072620153427,... | -0.049368 |
# Automatic group mapping fails Troubleshoot problems where the debugging data suggests a bad or nonexistent mapping between your Vault role and AD FS the Claim Issuance Policy. ## Example debugging data ```json [DEBUG] auth.saml.auth\_saml\_1d2227e7: validating user context for role: api=callback role\_name=default-sa... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/auth/saml/troubleshoot-adfs/bad-mapping.mdx | main | vault | [
-0.03296812251210213,
-0.004767115227878094,
-0.05406833812594414,
0.011386625468730927,
-0.044696688652038574,
-0.046767473220825195,
0.028394905850291252,
-0.02297982946038246,
0.0043739620596170425,
0.012554471381008625,
0.09195051342248917,
-0.06960976123809814,
0.031999628990888596,
0... | -0.055452 |
# Rollback or downgrade Vault plugins Downgrading a plugin in the catalog affects all uses of that plugin version. Always check the plugin release notes for unsupported transitions before starting your rollback or downgrade. ## Before you start - \*\*To register and downgrade official enterprise plugins, you must have ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/rollback.mdx | main | vault | [
0.04422089457511902,
-0.021825656294822693,
-0.0024754055775702,
-0.09553168714046478,
-0.011814521625638008,
-0.02868911810219288,
-0.11422538012266159,
-0.044299814850091934,
-0.04591083899140358,
0.02143711782991886,
0.049512263387441635,
0.04141896590590477,
-0.030958686023950577,
0.07... | -0.106615 |
# Register and enable external plugins An external plugin is any authentication or secrets plugin build from external code. Vault pre-registers commonly used external plugins (like `kv`), but you must manually add other external plugins to the Vault plugin catalog before you can use them with your Vault installation. I... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/register.mdx | main | vault | [
0.00722377048805356,
-0.07523763924837112,
-0.08470424264669418,
-0.027131740003824234,
-0.01598295569419861,
-0.01850927248597145,
-0.06759063154459,
0.03673386201262474,
0.013019345700740814,
-0.012275631539523602,
0.09377341717481613,
-0.02148211933672428,
-0.015333455987274647,
0.07032... | -0.001263 |
# Plugin architecture Plugins are separate, standalone applications with have predefined interfaces and parameters. Vault executes and communicates with plugins over RPC. Plugins do not share memory space with Vault and a crash in the plugin cannot crash the entirety of Vault. ## Plugin registration An important consid... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-architecture.mdx | main | vault | [
-0.008999884128570557,
-0.1057356521487236,
-0.0836566761136055,
-0.011232630349695683,
-0.024204956367611885,
0.007378188893198967,
-0.06468623131513596,
0.01093672588467598,
0.0012773218331858516,
-0.012456625699996948,
0.06417779624462128,
0.02792319469153881,
0.008477076888084412,
0.06... | -0.036055 |
establish a TLS connection, but you must set the [`api\_addr`](/vault/docs/configuration#api\_addr) parameter in your Vault configuration so manually registered plugins can establish communication with the Vault server at mount time. If the storage backend has HA enabled and supports automatic host address detection (e... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-architecture.mdx | main | vault | [
-0.014349161647260189,
0.0035952050238847733,
-0.060718487948179245,
0.016315937042236328,
-0.07182971388101578,
-0.07613357156515121,
-0.10288867354393005,
-0.010165249928832054,
0.05629391595721245,
0.006268012337386608,
0.0021048649214208126,
0.03076409175992012,
0.030246810987591743,
0... | -0.066034 |
# Plugin runtime settings ## Plugin environment variables An advantage for external plugins over builtin plugins is they can specify additional environment variables because they are run in their own process. -> Vault 1.16.0 changed the precedence given to plugin-specific environment variables so they take priority ove... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-management.mdx | main | vault | [
0.042637355625629425,
0.006928456015884876,
-0.0666864737868309,
-0.07482429593801498,
-0.0405169278383255,
-0.04556766152381897,
-0.04908904433250427,
0.012829187326133251,
-0.02158397063612938,
0.00032335438299924135,
0.0324593186378479,
-0.01699768751859665,
0.007389547768980265,
0.0861... | -0.107429 |
# The Vault plugin ecosystem Plugins act as building blocks in Vault that help you control how data moves through your environment and how clients access that data. Vault supports the following plugin types: - \*\*`auth`\*\* plugins handle authentication flows and allow clients to authenticate to Vault. - \*\*`secret`\... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/index.mdx | main | vault | [
-0.008259589783847332,
-0.03300613537430763,
-0.07664553821086884,
-0.0213699359446764,
-0.009813465178012848,
-0.05476371571421623,
-0.056841958314180374,
-0.041970375925302505,
0.0451846718788147,
-0.037406157702207565,
0.037179864943027496,
0.03804914280772209,
0.019905932247638702,
-0.... | -0.012893 |
- \*\*`aws`\*\* is version 1.18.5 of a built-in, embedded plugin. - \*\*`mykv`\*\* is version 1.0.0 of an external plugin. - \*\*`testkv`\*\* is an unversioned external plugin. ```shell-session $ vault plugin list secret Name Version ---- ------- aws v1.18.5+builtin.vault azure v0.20.1+builtin gcp v0.20.1+builtin gcpkm... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/index.mdx | main | vault | [
-0.042833175510168076,
0.05880522355437279,
-0.04409537836909294,
-0.048056598752737045,
0.0883069634437561,
-0.024654366075992584,
-0.005190341733396053,
-0.027539780363440514,
0.11137616634368896,
0.10780686885118484,
0.10210105776786804,
-0.0671885684132576,
0.03579947352409363,
0.02785... | -0.01403 |
# Event notifications development in Vault plugins @include 'alerts/enterprise-only.mdx' ~> Advanced topic! Plugin development is a highly advanced topic in Vault, and is not required knowledge for day-to-day usage. If you don't plan on writing any plugins, we recommend not reading this section of the documentation. [E... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-development-event-notifications.mdx | main | vault | [
0.06639695912599564,
-0.004292893689125776,
-0.06305745989084244,
-0.041690558195114136,
0.01849276013672352,
-0.044818200170993805,
0.018864721059799194,
-0.028084667399525642,
0.07960379868745804,
-0.06557048857212067,
0.023609044030308723,
-0.019682740792632103,
0.014152091927826405,
0.... | 0.016418 |
what edition of Vault they are connected to and should generate events regardless. ## Examples Here are some examples of adding event notifications to the KV and database plugins in Vault: - https://github.com/hashicorp/vault-plugin-secrets-kv/pull/88 - https://github.com/hashicorp/vault/pull/24718 | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-development-event-notifications.mdx | main | vault | [
0.030289234593510628,
-0.003109120763838291,
-0.0811341255903244,
-0.0054042586125433445,
-0.02309400960803032,
0.008393621072173119,
-0.0694228857755661,
-0.024518292397260666,
0.0906883031129837,
-0.05326509475708008,
0.018137723207473755,
-0.0294652096927166,
0.024794340133666992,
0.033... | 0.013003 |
# Plugin development ~> Advanced topic! Plugin development is a highly advanced topic in Vault, and is not required knowledge for day-to-day usage. If you don't plan on writing any plugins, we recommend not reading this section of the documentation. Because Vault communicates to plugins over a RPC interface, you can bu... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-development.mdx | main | vault | [
-0.07534901797771454,
-0.04550924524664879,
-0.07539468258619308,
-0.024652043357491493,
-0.06986735761165619,
-0.0457342267036438,
-0.05222319811582565,
0.034393277019262314,
-0.03482593595981598,
-0.012313613668084145,
0.022944755852222443,
-0.005498197395354509,
0.017451176419854164,
0.... | 0.031903 |
advantage of the SDK's [default logger](https://github.com/hashicorp/vault/blob/fe55cbbf05586ec4c0cd9bdf865ec6f741a8933c/sdk/framework/backend.go#L437). No additional setup is required. The logger can be used like the following: ```go func (b \*backend) example() { b.Logger().Trace("Trace level log") b.Logger().Debug("... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/plugin-development.mdx | main | vault | [
0.05195634067058563,
0.04675613343715668,
-0.11256646364927292,
-0.01795940101146698,
0.029028572142124176,
-0.09772098064422607,
-0.0196455679833889,
0.04870293661952019,
0.03575461357831955,
-0.034924548119306564,
0.04207678139209747,
-0.05384945869445801,
0.05061669647693634,
0.03325535... | 0.009395 |
# Upgrade plugins Upgrading a plugin in the catalog affects all uses of that plugin version. For example, if you have 5 different `customkv` mounts using v1.0.0 and you upgrade to v1.1.0, all the existing mounts will use the new binary if you overwrite it. We recommend treating plugin versions in the catalog as immutab... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/upgrade.mdx | main | vault | [
0.006306237541139126,
-0.048532675951719284,
0.022993795573711395,
-0.0556090846657753,
0.000020068506273673847,
-0.05011841282248497,
-0.0736735463142395,
-0.03273913264274597,
-0.0008163036545738578,
0.011570235714316368,
0.06585633754730225,
0.019923746585845947,
-0.0297786183655262,
0.... | -0.034373 |
# Add a containerized secrets plugin to Vault Run your external secrets plugins in containers to increases the isolation between the plugin and Vault. ## Before you start - \*\*Your Vault instance must be running on Linux\*\*. - \*\*Your Vault instance must have local access to the Docker Engine API\*\*. Vault uses the... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/containerized-plugins/add-a-containerized-plugin.mdx | main | vault | [
-0.022550327703356743,
-0.003723238129168749,
-0.05523759499192238,
-0.04310525953769684,
0.021312586963176727,
-0.07206360995769501,
-0.05492814630270004,
0.03846701234579086,
-0.016048911958932877,
0.003287781961262226,
0.03731922060251236,
-0.027511022984981537,
0.016061371192336082,
0.... | -0.067221 |
secret my-kv-container ``` 1. Enable the new plugin for your Vault instance with `vault secrets enable` and the new plugin ID: ```shell-session $ vault secrets enable NEW\_PLUGIN\_ID ``` For example: ```shell-session $ vault secrets enable my-kv-container ``` You can provide additional information about the image entry... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/containerized-plugins/add-a-containerized-plugin.mdx | main | vault | [
0.018904106691479683,
0.01803463324904442,
-0.05040865018963814,
0.011012070812284946,
-0.007956488057971,
-0.0045747035183012486,
-0.043088942766189575,
0.0603075735270977,
-0.010607006959617138,
0.0292704775929451,
0.05351640656590462,
-0.11357180029153824,
0.028891989961266518,
0.076938... | -0.060755 |
# Containerized plugins overview Support for the `container` runtime is currently limited to Linux. Vault has a wide selection of builtin plugins to support integrating with other systems. For example, you can use plugins to exchange app identity information with an authentication service to receive a Vault token, or m... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/containerized-plugins/index.mdx | main | vault | [
0.023998942226171494,
-0.03214510530233383,
-0.05659625306725502,
-0.021993404254317284,
-0.011765839532017708,
-0.03309931978583336,
-0.05997283011674881,
0.06407856196165085,
0.005181405693292618,
-0.0057017127983272076,
-0.009355118498206139,
-0.01794535480439663,
0.014257773756980896,
... | 0.019713 |
plugin containers can use the "plugin runtime" APIs for finer grained settings. See the CLI documentation for [`vault plugin runtime`](/vault/docs/commands/plugin/runtime) for more details. | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/plugins/containerized-plugins/index.mdx | main | vault | [
0.04256359115242958,
0.01968354359269142,
-0.0815420150756836,
-0.0036798003129661083,
-0.05242596194148064,
-0.08745456486940384,
-0.06938798725605011,
0.03241608291864395,
-0.06133992597460747,
-0.040424395352602005,
-0.011546268127858639,
-0.009245168417692184,
0.030656222254037857,
-0.... | 0.030341 |
# Run Vault as a service Instead of starting your Vault server manually from the command line, you can configure a service to start Vault automatically. ## Before you start - \*\*You must install Vault\*\*. You can [use a package manager](/vault/install) or [install a binary manually](/vault/docs/install/install-binary... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-service.mdx | main | vault | [
0.06680066883563995,
-0.028272230178117752,
-0.07794243097305298,
-0.07129114121198654,
-0.06811853498220444,
-0.0176127590239048,
-0.08340584486722946,
0.020305978134274483,
0.006782961543649435,
-0.007746357005089521,
-0.012240944430232048,
0.012709232978522778,
0.03734535351395607,
0.08... | -0.09577 |
```powershell Start-Service -Name MS\_VAULT ``` 1. Confirm service status: ```powershell Get-Service -Name MS\_VAULT Status Name DisplayName ------ ---- ----------- Running MS\_VAULT Vault Service ``` ## Step 3: Verify the service is running To confirm the service is running and your Vault service is available, open th... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-service.mdx | main | vault | [
0.07041073590517044,
-0.02844858728349209,
-0.07110780477523804,
-0.02699292078614235,
0.015873603522777557,
-0.04676579311490059,
-0.04027201235294342,
-0.05594322085380554,
-0.029326708987355232,
-0.02209116332232952,
0.024328500032424927,
-0.03618351370096207,
0.052410874515771866,
0.04... | -0.06243 |
# Why use TLS? You can enhance the overall security posture of your Vault cluster when you secure communications with TLS to ensure that data transmitted between Vault nodes and clients remains confidential and tamper-proof. @include 'ld-images/deploy/secure-vault-tls.mdx' Use mutual TLS with your Vault cluster deploym... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/why-use-tls.mdx | main | vault | [
-0.007531245704740286,
0.10375545173883438,
0.01374566089361906,
-0.07075382769107819,
-0.013547574169933796,
-0.041319381445646286,
0.01062984112650156,
-0.019188521429896355,
0.06497424095869064,
-0.0453890822827816,
-0.020471304655075073,
0.04479129612445831,
0.15214447677135468,
0.0210... | 0.00853 |
# Run Vault on IBM z/OS Container Extensions (zCX) Deploy a fully secured 3-node HashiCorp Vault Enterprise cluster on IBM z/OS Container Extensions (zCX). ## Before you start - \*\*Read about [sealing and unsealing](/vault/docs/concepts/seal) Vault\*\*. You cannot test your deployment without unsealing Vault. - \*\*In... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-zcx-cluster.mdx | main | vault | [
-0.00518299313262105,
0.058734387159347534,
-0.08122394979000092,
-0.03474747762084007,
-0.01427858043462038,
-0.06257141381502151,
-0.05958506837487221,
0.014388545416295528,
-0.03960886225104332,
-0.06113579496741295,
0.0037420769222080708,
-0.038118574768304825,
0.09392613917589188,
-0.... | 0.026029 |
: volumes: - vault-config:/vault/config env\_file: - path: required: true networks: - build: include: - path: ``` For example: ```yaml name: zcx services: vault-base: volumes: - vault-config:/vault/config env\_file: - path: ./vault.env required: true networks: - vault\_cluster build: include: - path: ../shared-deploy/c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-zcx-cluster.mdx | main | vault | [
0.034878771752119064,
0.024523405358195305,
-0.08000655472278595,
-0.0049588666297495365,
0.01351223886013031,
-0.050546757876873016,
-0.012480934150516987,
0.03673875704407692,
-0.009298081509768963,
-0.023412765935063362,
-0.0033371723257005215,
-0.039573635905981064,
0.06968777626752853,
... | -0.044749 |
--- plugin\_directory = "/vault/plugins/" plugin\_tmpdir = "/vault/plugins/tmp" # --- Listener configuration --- listener "tcp" { address = "[::]:8200" tls\_disable = "false" tls\_cert\_file = "/vault/config/certs/vault.pem" tls\_key\_file = "/vault/config/certs/vault.key" tls\_client\_ca\_file = "/vault/config/certs/c... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-zcx-cluster.mdx | main | vault | [
-0.01740489900112152,
0.07951183617115021,
-0.04775771126151085,
0.016180071979761124,
0.0018743985565379262,
-0.04066759720444679,
-0.004098489414900541,
-0.004702369682490826,
0.03620224818587303,
-0.03281831741333008,
0.023156121373176575,
-0.06418274343013763,
0.10505898296833038,
0.04... | -0.035296 |
timeout client 1m timeout server 1m log global # --- Stats Page (HTTPS) --- frontend stats bind \*:8404 ssl crt /usr/local/etc/haproxy/haproxy.pem mode http stats enable stats uri /stats stats refresh 10s stats admin if TRUE # --- Vault API Frontend (TLS Passthrough) --- frontend vault\_api bind \*:8200 # Listen on Vau... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/run-as-zcx-cluster.mdx | main | vault | [
-0.023758213967084885,
0.11922822892665863,
-0.11246079951524734,
0.005859456956386566,
-0.02993273176252842,
-0.08016427606344223,
-0.058027978986501694,
0.01624212972819805,
0.0038853471633046865,
-0.021765513345599174,
-0.051975708454847336,
0.011974546127021313,
0.08791674673557281,
-0... | -0.055071 |
# Vault Lambda extension AWS Lambda lets you run code without provisioning and managing servers. The [Vault Lambda Extension](https://github.com/hashicorp/vault-lambda-extension) utilizes the AWS Lambda Extensions API to help your Lambda function read secrets from your Vault deployment. You can use the [quick-start](ht... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/lambda-extension.mdx | main | vault | [
-0.017610082402825356,
0.0316629558801651,
-0.10218583047389984,
-0.0040365238673985004,
-0.03348323330283165,
-0.06387165933847427,
-0.03188147023320198,
0.02273915521800518,
0.05596419423818588,
0.02171887829899788,
0.01557666901499033,
-0.01629338413476944,
0.05573556199669838,
-0.00734... | -0.028731 |
authenticate as. Must be configured for the ARN of your Lambda's role. ```shell-session $ VAULT\_AUTH\_ROLE=vault-lambda-role ``` The path to a secret in Vault. Can be static or dynamic. Unless VAULT\_SECRET\_FILE is specified, JSON response will be written to `/tmp/vault/secret.json`. ```shell-session $ VAULT\_SECRET\... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/lambda-extension.mdx | main | vault | [
-0.026305226609110832,
0.07929681986570358,
-0.11418028920888901,
-0.029962023720145226,
-0.042652398347854614,
-0.05977717787027359,
-0.004475461784750223,
0.05076133832335472,
0.028858453035354614,
-0.021473251283168793,
0.01694255881011486,
0.01568152755498886,
0.0018404952716082335,
0.... | -0.069155 |
exactly as described in the [Vault Commands (CLI)](/vault/docs/commands#environment-variables) documentation. However, note that `VAULT\_CLIENT\_TIMEOUT` cannot extend the timeout beyond the 10s initialization timeout imposed by the Extensions API when writing files to disk. | Environment variable | Description | Requi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/lambda-extension.mdx | main | vault | [
0.07254038006067276,
0.05561727285385132,
-0.05153530463576317,
-0.009250732138752937,
-0.011152776889503002,
-0.05309031903743744,
-0.09426575899124146,
0.00835676584392786,
0.03786299750208855,
-0.04528113082051277,
0.024551037698984146,
-0.013817586936056614,
0.04870138317346573,
-0.018... | -0.097373 |
where caching makes sense without negative impact in others. To turn on caching, set the environment variable `VAULT\_DEFAULT\_CACHE\_TTL` to a valid value that is parsable as a time.Duration in Go, for example, "15m", "1h", "2m3s" or "1h2m3s", depending on application needs. An invalid or negative value will be treate... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/lambda-extension.mdx | main | vault | [
0.022229420021176338,
0.06071789935231209,
-0.03776603937149048,
-0.006711719557642937,
-0.042375560849905014,
-0.1026865616440773,
0.0012531756656244397,
-0.04358644038438797,
0.08512888848781586,
0.0007189273019321263,
0.008343272842466831,
0.06674171984195709,
0.017201049253344536,
-0.0... | -0.107239 |
related statistics to help assess the cost impact of this extension. Note that AWS Lambda allocates [CPU power in proportion to memory](https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html) so results will vary widely. These benchmarks were run with the minimum 128MB of memory allocated so aim to give... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/lambda-extension.mdx | main | vault | [
-0.023382939398288727,
0.022485895082354546,
-0.09278978407382965,
0.039460863918066025,
-0.009141121059656143,
-0.002829300006851554,
-0.03295298293232918,
0.04922350123524666,
0.008393615484237671,
0.007765295449644327,
0.007833348587155342,
0.0072919330559670925,
-0.00023742177290841937,
... | -0.017726 |
# Running Vault ## Launching the Vault AMI When Vault is first launched from an official Marketplace AMI, it will come up in an uninitialized state and must be initialized via the [API](/vault/api-docs/system/init), [CLI](/vault/docs/commands/operator/init), or UI. The Marketplace AMI listens on port 8200 by default. I... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/aws/run.mdx | main | vault | [
0.03214956447482109,
0.024640250951051712,
-0.03565449267625809,
-0.046560563147068024,
-0.02652948535978794,
-0.046055544167757034,
-0.034738779067993164,
0.03731555864214897,
0.020857244729995728,
-0.023217253386974335,
0.04048721119761467,
-0.01584473066031933,
0.06630297005176544,
0.05... | 0.025579 |
# Kubernetes integrations comparison HashiCorp Vault provides three different integrations to help Kubernetes workloads consume secrets from Vault without modifying application code. Each integration has unique characteristics that make it suitable for different use cases. Use the information below to compare the avail... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/comparisons.mdx | main | vault | [
0.014548555947840214,
0.050921086221933365,
-0.03214170038700104,
-0.05992812663316727,
-0.03282683715224266,
-0.04635060951113701,
-0.056248247623443604,
0.006034357938915491,
0.05585520714521408,
-0.04660943150520325,
0.024333538487553596,
-0.008144374005496502,
0.024383608251810074,
-0.... | 0.068729 |
between integrations based on their architectural patterns. - \*\*Vault Secrets Operator\*\* - Lowest load due to CRD-specific connections and cluster-local secret caching. Single manager for an entire cluster. - \*\*Vault Secrets Operator with CSI driver\*\* - Lower load due to one Vault connection pool per Node, with... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/comparisons.mdx | main | vault | [
0.025015614926815033,
-0.005985544994473457,
-0.01237508561462164,
-0.02902223728597164,
-0.014534393325448036,
-0.038949571549892426,
-0.004837264306843281,
0.01626787707209587,
0.030303511768579483,
0.007221775595098734,
0.04146683216094971,
0.001232530572451651,
0.037966612726449966,
-0... | 0.191774 |
# Migrate Consul to Raft storage This procedure assumes you have a Vault cluster deployed in a Kubernetes environment configured with Consul storage. The storage migration can occur while leaving the Consul cluster intact. A single change to the Consul cluster is a lock file written by Vault during the migration. This ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/consul-to-raft.mdx | main | vault | [
-0.000661956612020731,
-0.0009301744867116213,
-0.052689433097839355,
-0.049399878829717636,
0.012153935618698597,
-0.04776957258582115,
-0.07111170142889023,
0.0033768818248063326,
0.0017780994530767202,
0.04761650785803795,
0.036343030631542206,
0.0024012625217437744,
0.026770412921905518,... | 0.008395 |
# Run Vault on Kubernetes Vault can be deployed into Kubernetes using the official HashiCorp Vault Helm chart. The Helm chart allows users to deploy Vault in various configurations: - Dev: a single in-memory Vault server for testing Vault - Standalone (default): a single Vault server persisting to a volume using the fi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/index.mdx | main | vault | [
0.04336364567279816,
-0.01752614416182041,
-0.0320260114967823,
-0.07181814312934875,
-0.054985374212265015,
-0.020144883543252945,
-0.08593934774398804,
0.03551851958036423,
0.08434051275253296,
-0.0064674485474824905,
-0.0011800677748396993,
0.017278172075748444,
0.04000693932175636,
-0.... | 0.134008 |
# Vault Agent Injector vs. Vault CSI Provider This document explores two different methods for integrating HashiCorp Vault with Kubernetes. The information provided is intended for DevOps practitioners who understand secret management concepts and are familiar with HashiCorp Vault and Kubernetes. This document also off... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/injector-csi.mdx | main | vault | [
0.005997569765895605,
0.0739874467253685,
-0.03578304126858711,
-0.014201619662344456,
-0.009852342307567596,
-0.005042249336838722,
0.0026749451644718647,
0.00006788635801058263,
0.058055903762578964,
0.03572814539074898,
0.036983318626880646,
0.018491026014089584,
0.059430789202451706,
0... | 0.152025 |
vary in size. You need to consider the secret types your application requires and how they’re projected into the application. - \*\*Secret definition:\*\* You also need to consider how each secret is defined, created, updated, and removed, as well as the tooling associated with that process. - \*\*Encryption:\*\* Encry... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/injector-csi.mdx | main | vault | [
-0.02993607148528099,
-0.016063267365098,
0.0279989130795002,
-0.05645855888724327,
-0.050106991082429886,
0.0035733345430344343,
0.011799332685768604,
0.02743607945740223,
0.07406537234783173,
0.013004034757614136,
-0.044590286910533905,
-0.003624943783506751,
0.001477800658904016,
-0.057... | 0.126955 |
considerations: - The Sidecar Agent Injector solution is composed of two elements: - The Sidecar Service Injector, which is deployed as a cluster service and is responsible for intercepting Kubernetes apiserver pod events and mutating pod specs to add required sidecar containers - The Vault Sidecar Container, which is ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/injector-csi.mdx | main | vault | [
0.010010129772126675,
0.06230172887444496,
-0.022345231845974922,
-0.029580898582935333,
0.01937255635857582,
-0.013196500949561596,
-0.01049551647156477,
0.021996958181262016,
-0.004710048902779818,
0.006003239192068577,
0.06448262184858322,
-0.015861615538597107,
0.02783057652413845,
0.0... | 0.151731 |
they are running. ## Summary Designing secrets management in Kubernetes is an intricate task. There are multiple approaches, each with its own set of attributes. We recommend exploring the options presented in this document to increase your understanding of the internals and decide on the best option for your use case.... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/injector-csi.mdx | main | vault | [
0.010696048848330975,
0.033933646976947784,
-0.015573753975331783,
-0.022559819743037224,
-0.016443422064185143,
-0.03233819082379341,
-0.04186360910534859,
-0.02798343263566494,
0.03892185539007187,
0.014883177354931831,
0.04212530329823494,
-0.0011150377104058862,
-0.0010818848386406898,
... | 0.115379 |
# Vault Secrets Store CSI provider examples The following examples demonstrate common uses of the Vault Secrets Store CSI provider. ## File based dynamic database credentials The following Secret Provider Class retrieves dynamic database credentials from Vault and extracts the generated username and password. The secre... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/examples.mdx | main | vault | [
-0.027800559997558594,
0.009948499500751495,
-0.06945358961820602,
-0.009184688329696655,
-0.03689996153116226,
-0.023605866357684135,
0.019287554547190666,
0.04283244162797928,
0.046430058777332306,
0.023880653083324432,
0.02769201062619686,
-0.00040797385736368597,
0.07194937765598297,
0... | 0.03416 |
# Vault Secrets Store CSI provider The Vault Secrets Store CSI provider allows pods to consume Vault secrets using [Secrets Store CSI](https://github.com/kubernetes-sigs/secrets-store-csi-driver) volumes. ~> The Vault Secrets Store CSI provider requires the [CSI Secret Store](https://github.com/kubernetes-sigs/secrets-... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/index.mdx | main | vault | [
-0.012935607694089413,
0.0006407419568859041,
0.003877258626744151,
-0.005338489543646574,
0.016308074817061424,
-0.005063645076006651,
0.020451780408620834,
-0.002524596406146884,
0.08968901634216309,
0.02349686436355114,
0.044572196900844574,
0.025953680276870728,
0.028493143618106842,
-... | 0.130178 |
app: demo replicas: 1 template: spec: serviceAccountName: app containers: - name: app image: my-app:1.0.0 volumeMounts: - name: 'vault-db-creds' mountPath: '/mnt/secrets-store' readOnly: true volumes: - name: vault-db-creds csi: driver: 'secrets-store.csi.k8s.io' readOnly: true volumeAttributes: secretProviderClass: 'v... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/index.mdx | main | vault | [
0.012098211795091629,
0.03193594515323639,
-0.02154230885207653,
-0.0649079754948616,
-0.015332250855863094,
-0.015490989200770855,
-0.030113065615296364,
0.04491294175386429,
0.08125913143157959,
0.0193310659378767,
0.025139734148979187,
-0.053985774517059326,
0.08129938691854477,
0.02247... | -0.00779 |
# Vault Secrets Store CSI provider configurations The following command line arguments are supported by the Vault Secrets Store CSI provider. Most settings support being set by, in ascending order of precedence: - Environment variables - Command line arguments - Secret Provider Class parameters If installing via the he... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/configurations.mdx | main | vault | [
0.04647138714790344,
0.02510596066713333,
-0.06579847633838654,
-0.03250183165073395,
-0.026887742802500725,
-0.07834532856941223,
-0.03882940113544464,
0.03397540748119354,
0.04613181948661804,
0.006826428230851889,
0.03550434485077858,
0.03291282802820206,
0.058885589241981506,
0.0244609... | 0.004537 |
installing the helm chart. The Helm chart installs Vault Agent as a sidecar to the Vault Secrets Store CSI provider for caching and renewals. Setting `vaultAddress` here causes the Vault Secrets Store CSI provider to bypass the Vault Agent cache. - `vaultNamespace` `(string: "")` - The Vault [namespace](/vault/docs/ent... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/configurations.mdx | main | vault | [
-0.020211273804306984,
0.03961459919810295,
-0.04457099363207817,
-0.040055613964796066,
-0.006105242297053337,
-0.06033594533801079,
-0.09903090447187424,
-0.003967329394072294,
0.032274357974529266,
-0.018528901040554047,
0.027111466974020004,
-0.0067255375906825066,
0.1171758770942688,
... | -0.116405 |
# Install the Vault Secrets Store CSI provider ## Prerequisites - Kubernetes 1.16+ for both the master and worker nodes (Linux-only) - [Secrets Store CSI driver](https://secrets-store-csi-driver.sigs.k8s.io/getting-started/installation.html) installed. - `TokenRequest` endpoint available, which requires setting the fla... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/csi/installation.mdx | main | vault | [
0.014464863575994968,
0.012858959846198559,
0.01113987248390913,
-0.06737380474805832,
-0.042908262461423874,
-0.016254939138889313,
-0.06969421356916428,
-0.0009016924304887652,
0.06498847901821136,
0.047458216547966,
-0.004364500287920237,
-0.03524754196405411,
0.05430542305111885,
0.003... | 0.092589 |
# Vault Secrets Operator examples The Operator project provides the following examples: - Sample use-cases are documented [here](https://github.com/hashicorp/vault-secrets-operator#samples) - A Terraform based demo can be found [here](https://github.com/hashicorp/vault-secrets-operator/tree/main/demo) ## JWT auth for K... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/examples.mdx | main | vault | [
-0.0012013032101094723,
0.07984151691198349,
-0.014072091318666935,
-0.036245010793209076,
-0.02666037529706955,
-0.047566406428813934,
-0.03595893830060959,
-0.014490569941699505,
0.06135321781039238,
-0.011721731163561344,
-0.02263566665351391,
-0.027214238420128822,
0.050696808844804764,
... | 0.069061 |
# Vault Secrets Operator Helm chart configuration The chart is customizable using [Helm configuration values](https://helm.sh/docs/intro/using\_helm/#customizing-the-chart-before-installing). ## Top-Level Stanzas Use these links to navigate to a particular top-level stanza. - [`controller`](#h-controller) - [`metricsSe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.015183919109404087,
0.05786664038896561,
-0.03828879073262215,
-0.08366809785366058,
-0.051487330347299576,
-0.024306632578372955,
-0.03673211857676506,
0.019714655354619026,
0.02361285872757435,
0.009125061333179474,
0.05253288894891739,
-0.039297111332416534,
0.042668018490076065,
-0.0... | 0.017444 |
- "HCPAuth" - `userFacingRoles` ((#v-controller-rbac-clusterroleaggregation-userfacingroles)) (`object: ""`) - userFacingRoles is a map of roles that will be aggregated into the viewer and editor ClusterRoles. See https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles for more information. - `v... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.037363115698099136,
-0.023931484669446945,
-0.04307324066758156,
0.07415521889925003,
-0.0010045248782262206,
0.11609804630279541,
-0.010489381849765778,
-0.03766566514968872,
0.04671843722462654,
0.04391568899154663,
-0.018949978053569794,
-0.10591842979192734,
0.022191844880580902,
-0.... | 0.068716 |
operator search for a "default" VaultAuthGlobal if none is specified on the referring VaultAuth CR. Default: true - `backoffOnSecretSourceError` ((#v-controller-manager-backoffonsecretsourceerror)) (`object: ""`) - Backoff settings for the controller manager. These settings control the backoff behavior when the control... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
-0.021560063585639,
0.04471582546830177,
-0.07803867012262344,
0.045206449925899506,
-0.020280810073018074,
-0.001401127316057682,
-0.05925992876291275,
-0.032100047916173935,
-0.005870063789188862,
-0.03396948426961899,
0.04100773110985756,
0.00012963802146259695,
0.023817094042897224,
-0... | -0.107126 |
configured when client cache persistence with encryption is enabled and will deploy an additional VaultAuthMethod to be used by the Vault Transit Engine. E.g. when `controller.manager.clientCache.persistenceModel=direct-encrypted` Supported Vault authentication methods for the Transit Auth method are: jwt, appRole, aws... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.01499142311513424,
0.011442573741078377,
-0.06104244291782379,
0.016440341249108315,
-0.0035544265992939472,
0.018799126148223877,
-0.029414428398013115,
-0.03946748375892639,
0.06470046192407608,
-0.00913450587540865,
0.006963575724512339,
-0.00102220568805933,
0.055749326944351196,
0.0... | -0.045888 |
Vault Auth Role to use This is a required field and must be setup in Vault prior to deploying the helm chart if using the AWS for the Transit auth method. - `region` ((#v-controller-manager-clientcache-storageencryption-aws-region)) (`string: ""`) - AWS region to use for signing the authentication request Optional, but... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.06782008707523346,
0.10886311531066895,
-0.08447272330522537,
-0.03790731355547905,
0.017719384282827377,
0.014807689934968948,
0.0240724366158247,
0.004495126660913229,
0.06260421127080917,
0.01689903624355793,
0.018787525594234467,
-0.10933662950992584,
0.0875559076666832,
0.0228219814... | -0.041644 |
at /var/run/podinfo. User-defined volumes cannot override this. Example: ```yaml volumes: - name: approle-secret secret: secretName: my-approle-secret defaultMode: 0400 - name: tls-certs configMap: name: vault-tls ``` - `resources` ((#v-controller-manager-resources)) (`map`) - Configures the default resources for the v... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.048744287341833115,
0.06378739327192307,
0.046434685587882996,
-0.026901356875896454,
-0.049476590007543564,
-0.046863459050655365,
-0.026333218440413475,
0.0030571846291422844,
0.059803593903779984,
0.010527833364903927,
-0.056965701282024384,
-0.02384914644062519,
-0.009799452498555183,
... | 0.022982 |
(`boolean: false`) - toggles the deployment of the VaultAuthMethod CR - `namespace` ((#v-defaultauthmethod-namespace)) (`string: ""`) - Vault namespace for the VaultAuthMethod CR - `allowedNamespaces` ((#v-defaultauthmethod-allowednamespaces)) (`array: []`) - Kubernetes namespace glob patterns which are allow-listed fo... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.020800767466425896,
0.05089243873953819,
-0.03563448414206505,
-0.052768364548683167,
-0.005084597039967775,
-0.011263353750109673,
-0.03156627342104912,
-0.04595351219177246,
0.015783580020070076,
-0.00806337222456932,
0.05268355458974838,
-0.0697859451174736,
0.03997012972831726,
0.026... | -0.012518 |
STS endpoint to use; if not set will use the default - `iamEndpoint` ((#v-defaultauthmethod-aws-iamendpoint)) (`string: ""`) - The IAM endpoint to use; if not set will use the default - `secretRef` ((#v-defaultauthmethod-aws-secretref)) (`string: ""`) - The name of a Kubernetes Secret which holds credentials for AWS. S... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
-0.024227075278759003,
0.025778746232390404,
-0.025974491611123085,
-0.033803168684244156,
-0.06654487550258636,
0.044600386172533035,
0.08052372932434082,
-0.016943294554948807,
0.11734377592802048,
0.10721135884523392,
0.014163346961140633,
-0.11763426661491394,
0.02519591525197029,
-0.0... | 0.140453 |
common to all hooks. - `limits` ((#v-hooks-resources-limits)) - `cpu` ((#v-hooks-resources-limits-cpu)) (`string: 500m`) - `memory` ((#v-hooks-resources-limits-memory)) (`string: 128Mi`) - `requests` ((#v-hooks-resources-requests)) - `cpu` ((#v-hooks-resources-requests-cpu)) (`string: 10m`) - `memory` ((#v-hooks-resour... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.0042320359498262405,
0.08470217883586884,
-0.0376659519970417,
-0.013645132072269917,
0.05487549304962158,
-0.0014879165682941675,
-0.08304973691701889,
0.010216438211500645,
-0.04650849476456642,
0.012180608697235584,
0.020778821781277657,
-0.016383865848183632,
-0.049664635211229324,
-... | 0.042517 |
in milliseconds (e.g. 1695382800000) - nano - Unix timestamp in nanoseconds (e.g. 1695382800000000000) - iso8601 - ISO 8601 format (e.g. 2023-09-22T10:00:00Z) - rfc3339 - RFC 3339 format (e.g. 2023-09-22T10:00:00Z) - rfc3339nano - RFC 3339 format with nanosecond precision (e.g. 2023-09-22T10:00:00.123456789Z) Default: ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.011007653549313545,
-0.02480849251151085,
-0.05765044316649437,
0.004172299988567829,
0.041777513921260834,
-0.060525014996528625,
-0.08178439736366272,
0.07194219529628754,
0.0327860563993454,
-0.0057648057118058205,
0.048199284821748734,
-0.04244791716337204,
-0.04095086082816124,
-0.0... | 0.10743 |
the `default` ServiceAccount. ```yaml # config.yaml defaultVaultConnection: enabled: true defaultAuthMethod: enabled: true ``` ## Customizing the helm chart If you need to extend the Helm chart with additional options, we recommend using a third-party tool, such as [kustomize](https://github.com/kubernetes-sigs/kustomi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/helm.mdx | main | vault | [
0.051120296120643616,
0.06585244089365005,
-0.03014228120446205,
-0.0467817559838295,
-0.06983307749032974,
0.0034339423291385174,
-0.05823906511068344,
0.02103540487587452,
0.05710321664810181,
-0.0007572483737021685,
0.039453621953725815,
-0.01914121024310589,
0.035012003034353256,
0.018... | 0.002444 |
# Vault Secrets Operator The Vault Secrets Operator (VSO) allows Pods to consume Vault secrets natively from Kubernetes Secrets. The Vault Secrets Operator (VSO) is a fully supported component of HashiCorp Vault. ## Overview The Vault Secrets Operator operates by watching for changes to its supported set of Custom Reso... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/index.mdx | main | vault | [
0.010451249778270721,
0.033057425171136856,
-0.023765811696648598,
-0.017482634633779526,
0.0007662143325433135,
-0.03379309922456741,
-0.018774956464767456,
-0.01135176420211792,
0.07167400419712067,
0.013489252887666225,
0.034908074885606766,
-0.005733815487474203,
0.01848590560257435,
-... | 0.169143 |
# Vault Secrets Operator telemetry The Vault Secrets Operator is instrumented with Prometheus metrics in the following ways: \* The operator will emit the default controller-runtime metrics as outlined in the [monitoring](https://book-v1.book.kubebuilder.io/beyond\_basics/controller\_metrics.html) \* Custom metrics rel... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/telemetry.mdx | main | vault | [
-0.0030200013425201178,
0.05408566817641258,
-0.057888537645339966,
-0.05109699070453644,
-0.09862867742776871,
-0.09109248220920563,
-0.025301525369286537,
0.016364803537726402,
0.07135836780071259,
-0.026523109525442123,
0.03149274364113808,
-0.069505974650383,
0.0062574720941483974,
-0.... | 0.162464 |
# API Reference ## Packages - [secrets.hashicorp.com/v1beta1](#secretshashicorpcomv1beta1) ## secrets.hashicorp.com/v1beta1 Package v1beta1 contains API Schema definitions for the secrets v1beta1 API group ### Resource Types - [CSISecrets](#csisecrets) - [CSISecretsList](#csisecretslist) - [HCPAuth](#hcpauth) - [HCPAut... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.040023040026426315,
0.0345316007733345,
-0.07918687909841537,
-0.08077258616685867,
0.0027651910204440355,
-0.0018045713659375906,
-0.010191326029598713,
-0.036747343838214874,
-0.012292574159801006,
-0.06325028091669083,
0.032162755727767944,
-0.045019108802080154,
0.03919889032840729,
... | 0.063147 |
--- | | `containerState` \_[ContainerState](#containerstate)\_ | ContainerState is the state of the container that the CSI driver always sync on. This configuration is useful to sync when the last state of the container is in the terminated state and the restart count is greater than 0. | | | #### ContainerState \_Appe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.020374031737446785,
0.06324685364961624,
-0.02881265990436077,
-0.027852525934576988,
0.01534622348845005,
0.015872284770011902,
0.08163411170244217,
-0.025707153603434563,
0.004777413792908192,
-0.023553412407636642,
0.03517705574631691,
-0.04875010997056961,
0.08231481164693832,
0.023... | 0.184411 |
| Default | Validation | | --- | --- | --- | --- | | `organizationID` \_string\_ | OrganizationID of the HCP organization. | | | | `projectID` \_string\_ | ProjectID of the HCP project. | | | | `allowedNamespaces` \_string array\_ | AllowedNamespaces Kubernetes Namespaces which are allow-listed for use with this AuthMe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
0.019288701936602592,
0.038488831371068954,
-0.023661458864808083,
-0.06640701740980148,
-0.08073687553405762,
-0.017021842300891876,
-0.006604878697544336,
-0.10252005606889725,
0.05722369998693466,
-0.03369944170117378,
-0.021682046353816986,
-0.060811903327703476,
0.08133351057767868,
0... | 0.018758 |
Vault Secrets App \_Appears in:\_ - [HCPVaultSecretsAppStatus](#hcpvaultsecretsappstatus) | Field | Description | Default | Validation | | --- | --- | --- | --- | | `name` \_string\_ | Name of the dynamic secret | | | | `createdAt` \_string\_ | CreatedAt is the timestamp string of when the dynamic secret was created | ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.07415254414081573,
0.07788015156984329,
-0.10295996069908142,
-0.015677953138947487,
0.010313810780644417,
-0.002035736571997404,
0.022566070780158043,
0.008970205672085285,
0.06717737764120102,
-0.07708700746297836,
0.06413839757442474,
0.001208956935442984,
0.048761896789073944,
-0.05... | 0.014008 |
\_string\_ | Name of the resource | | | #### SecretCollection \_Appears in:\_ - [CSISecretsSpec](#csisecretsspec) | Field | Description | Default | Validation | | --- | --- | --- | --- | | `transformation` \_[Transformation](#transformation)\_ | Transformation provides configuration for transforming the secret data bef... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.0649322047829628,
0.05721784010529518,
-0.13188627362251282,
-0.03373219445347786,
0.01360621489584446,
-0.016937825828790665,
0.058406464755535126,
0.01349857822060585,
0.002328737871721387,
-0.05158515274524689,
0.04546500742435455,
-0.04058671370148659,
0.08129525184631348,
-0.015365... | 0.079334 |
Vault. | | | | `keyName` \_string\_ | KeyName to use for encrypt/decrypt operations via Vault Transit. | | | #### SyncConfig SyncConfig configures sync behavior from Vault to VSO \_Appears in:\_ - [VaultStaticSecretSpec](#vaultstaticsecretspec) | Field | Description | Default | Validation | | --- | --- | --- | --- | | ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.032870952039957047,
0.052632320672273636,
-0.033570826053619385,
0.031132051721215248,
0.00005725690789404325,
-0.00833350233733654,
0.003287182655185461,
-0.01503536757081747,
0.04273109883069992,
-0.04757171496748924,
0.020643122494220734,
-0.02432222291827202,
-0.01712966337800026,
-... | 0.097308 |
in this TransformationRef. If empty, then all templates from the SecretTransformation will be rendered to the K8s Secret. | | | | `ignoreIncludes` \_boolean\_ | IgnoreIncludes controls whether to use the SecretTransformation's Includes data key filters. | | | | `ignoreExcludes` \_boolean\_ | IgnoreExcludes controls whe... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.04166501387953758,
0.1241423636674881,
-0.024176325649023056,
0.017297616228461266,
0.0054418849758803844,
0.0006530514219775796,
0.002078389283269644,
-0.014154668897390366,
0.044140007346868515,
-0.0392167866230011,
0.029512042179703712,
-0.11590038239955902,
0.08567755669355392,
-0.0... | -0.075322 |
`secretRef` \_string\_ | SecretRef is the name of a Kubernetes Secret in the consumer's (VDS/VSS/PKI) namespace which holds credentials for AWS. Expected keys include `access\_key\_id`, `secret\_access\_key`, `session\_token` | | | | `irsaServiceAccount` \_string\_ | IRSAServiceAccount name to use with IAM Roles for Se... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.07332044094800949,
0.0431668646633625,
-0.029345110058784485,
-0.00965945515781641,
-0.003612461732700467,
-0.00024438370019197464,
0.046583179384469986,
-0.015964794903993607,
0.12483510375022888,
0.05403228849172592,
0.04463827610015869,
-0.08159907907247543,
0.040974073112010956,
-0.... | 0.089977 |
- [VaultAuthGlobalConfigKubernetes](#vaultauthglobalconfigkubernetes) - [VaultAuthSpec](#vaultauthspec) | Field | Description | Default | Validation | | --- | --- | --- | --- | | `role` \_string\_ | Role to use for authenticating to Vault. | | | | `serviceAccount` \_string\_ | ServiceAccount to use when authenticating ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.0040300339460372925,
0.0006933034746907651,
-0.07495244592428207,
0.00015583068307023495,
-0.02787182852625847,
-0.003977277781814337,
0.011016713455319405,
0.023003969341516495,
0.033510465174913406,
-0.026866348460316658,
0.006132146809250116,
-0.04155205190181732,
0.07762512564659119,
... | -0.039463 |
should be specified. | | | | `namespace` \_string\_ | Namespace to auth to in Vault | | | | `mount` \_string\_ | Mount to use when authenticating to auth method. | | | | `params` \_object (keys:string, values:string)\_ | Params to use when authenticating to Vault | | | | `headers` \_object (keys:string, values:string)\... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.018277358263731003,
0.020748065784573555,
-0.05960552394390106,
-0.016860542818903923,
-0.0446302704513073,
0.0005905802245251834,
0.0557030513882637,
-0.006287426222115755,
0.046444740146398544,
-0.026776893064379692,
0.011352552101016045,
-0.09828169643878937,
0.07429402321577072,
0.0... | 0.004569 |
| | | `tokenExpirationSeconds` \_integer\_ | TokenExpirationSeconds to set the ServiceAccount token. | 600 | Minimum: 600 | | `namespace` \_string\_ | Namespace to auth to in Vault | | | | `mount` \_string\_ | Mount to use when authenticating to auth method. | | | | `params` \_object (keys:string, values:string)\_ | Pa... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.003467332571744919,
0.02632618322968483,
-0.11376270651817322,
-0.006003796122968197,
-0.048691146075725555,
-0.04394741356372833,
0.007161333691328764,
0.036592788994312286,
-0.009111525490880013,
-0.0681002140045166,
0.013896691612899303,
-0.043286263942718506,
0.09524902701377869,
0.... | -0.007017 |
method will be used. This can be used as a default Vault namespace for all auth methods. | | | | `defaultAuthMethod` \_string\_ | DefaultAuthMethod to use when authenticating to Vault. | | Enum: [kubernetes jwt appRole aws gcp] | | `defaultMount` \_string\_ | DefaultMount to use when authenticating to auth method. If n... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
0.0002558580308686942,
0.03059895522892475,
-0.03997126594185829,
-0.04632771015167236,
-0.0557144396007061,
-0.02080593816936016,
-0.008031191304326057,
0.011154661886394024,
0.05704275891184807,
-0.015201748348772526,
0.014985610730946064,
-0.05660368502140045,
0.07707799226045609,
-0.00... | -0.007511 |
this check. Accepted values: []{"\*"} - wildcard, all namespaces. []{"a", "b"} - list of namespaces. unset - disallow all namespaces except the Operator's the VaultAuthMethod's namespace, this is the default behavior. | | | | `method` \_string\_ | Method to use when authenticating to Vault. | | Enum: [kubernetes jwt ap... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.0007544060354121029,
0.03647460415959358,
-0.010455080308020115,
-0.04618304595351219,
-0.031742267310619354,
-0.05133247748017311,
0.012246275320649147,
-0.07131964713335037,
0.056002020835876465,
-0.02876770682632923,
0.0021862778812646866,
-0.07634260505437851,
0.0937558114528656,
-0... | -0.027364 |
as the SNI host for TLS connections. | | | | `caCertSecretRef` \_string\_ | CACertSecretRef is the name of a Kubernetes secret containing the trusted PEM encoded CA certificate chain as `ca.crt`. CACertPath and CACertSecretRef are mutually exclusive, and only one should be specified. | | | | `caCertPath` \_string\_ | C... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
0.018212758004665375,
0.07338005304336548,
-0.0038735102862119675,
-0.02649136446416378,
-0.04230381175875664,
-0.03774254396557808,
-0.01684727519750595,
-0.0477784164249897,
0.1428350955247879,
-0.0197532307356596,
-0.01249916572123766,
-0.07200919091701508,
0.06172308698296547,
0.030435... | -0.000317 |
be ignored. See RequestHTTPMethod for more details. Please consult https://developer.hashicorp.com/vault/docs/secrets if you are uncertain about what 'params' should/can be set to. | | | | `renewalPercent` \_integer\_ | RenewalPercent is the percent out of 100 of the lease duration when the lease is renewed. Defaults t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
0.003481775289401412,
0.04569131135940552,
-0.062017571181058884,
-0.029313810169696808,
-0.08472263067960739,
-0.03572651371359825,
-0.03671451658010483,
-0.03703781217336655,
0.055676914751529694,
-0.021632308140397072,
0.07771120965480804,
0.03275945782661438,
0.06289145350456238,
0.027... | -0.012765 |
Vault to use when issuing TLS certificates. | | | | `revoke` \_boolean\_ | Revoke the certificate when the resource is deleted. | | | | `clear` \_boolean\_ | Clear the Kubernetes secret when the resource is deleted. | | | | `expiryOffset` \_string\_ | ExpiryOffset to use for computing when the certificate should be ren... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.012502294965088367,
0.12580999732017517,
-0.024114809930324554,
-0.0002619473380036652,
-0.043686963617801666,
-0.014001918025314808,
0.01593172363936901,
-0.017953483387827873,
0.13556896150112152,
-0.0380658395588398,
0.03401452675461769,
-0.0047453283332288265,
0.09290813654661179,
0... | 0.015975 |
format YYYY-MM-ddTHH:MM:SSZ | | | | `excludeCNFromSans` \_boolean\_ | ExcludeCNFromSans from DNS or Email Subject Alternate Names. Default: false | | | #### VaultSecretLease \_Appears in:\_ - [VaultDynamicSecretStatus](#vaultdynamicsecretstatus) | Field | Description | Default | Validation | | --- | --- | --- | --- | |... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.025720451027154922,
0.08950742334127426,
-0.054997723549604416,
-0.01593894325196743,
-0.002148226136341691,
-0.025871720165014267,
0.010728285647928715,
-0.03447388857603073,
0.06074800342321396,
-0.041422657668590546,
-0.008408991619944572,
-0.07228707522153854,
0.04960179328918457,
-... | -0.050759 |
\_string\_ | `secrets.hashicorp.com/v1beta1` | | | | `kind` \_string\_ | `VaultStaticSecretList` | | | | `metadata` \_[ListMeta](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#listmeta-v1-meta)\_ | Refer to Kubernetes API documentation for fields of `metadata`. | | | | `items` \_[VaultStaticSecret... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/api-reference.mdx | main | vault | [
-0.0003662318049464375,
0.07569248974323273,
-0.036908481270074844,
-0.03985225409269333,
-0.04664422571659088,
-0.013238613493740559,
0.02112514339387417,
0.004397254902869463,
0.03912322223186493,
-0.03347836062312126,
-0.007983366958796978,
-0.06310798227787018,
0.030491193756461143,
-0... | 0.093235 |
# Run the Vault Secrets Operator on OpenShift The Vault Secrets Operator may be installed on OpenShift clusters via the embedded OperatorHub or the Helm chart. OpenShift versions 4.12 and later are supported. ## OperatorHub The Vault Secrets Operator is certified by Red Hat and therefore included in the [OperatorHub se... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/openshift.mdx | main | vault | [
0.0903610959649086,
0.046926870942115784,
-0.029989996924996376,
0.0031366620678454638,
0.017230866476893425,
0.008016197942197323,
-0.0760292038321495,
-0.01957709901034832,
0.03956936299800873,
-0.014630971476435661,
-0.010932321660220623,
-0.02387692779302597,
-0.008508143946528435,
-0.... | 0.041511 |
# Secret data transformation Utilizing advanced templating and data filters, the Vault Secrets Operator for Kubernetes (VSO) can transform source secret data, secret metadata, resource labels and annotations into a format that is compatible with your application. All secret data sources are supported. Secret transforma... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/secret-transformation.mdx | main | vault | [
-0.016036223620176315,
0.12444920837879181,
-0.03538115322589874,
-0.02813156321644783,
-0.01995832286775112,
0.015025319531559944,
-0.018665585666894913,
0.012960805557668209,
0.0777389332652092,
-0.04349730536341667,
0.016664374619722366,
-0.06497576832771301,
-0.006027012597769499,
0.00... | 0.125196 |
a secret CR or within the same resource instance. ```yaml --- apiVersion: secrets.hashicorp.com/v1beta1 kind: SecretTransformation metadata: name: vso-templates namespace: example-vds spec: excludes: - password|username templates: url: text: '{{- template "dbUrl" . -}}' sourceTemplates: - name: helpers text: | {{/\* cr... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/secret-transformation.mdx | main | vault | [
-0.06126946955919266,
0.06963126361370087,
-0.05294211953878403,
-0.01039937324821949,
-0.012838343158364296,
0.015037178061902523,
-0.012815632857382298,
0.03843632712960243,
0.007749087642878294,
-0.01579442247748375,
-0.008549168705940247,
-0.06972157210111618,
0.024294551461935043,
-0.... | 0.015686 |
@include 'vso/common-links.mdx' # Install and upgrade the Vault Secrets Operator ## Prerequisites - A Kubernetes cluster running 1.23+ - Helm 3.7+ - [Optional] Kustomize 4.5.7+ ## Installation using Helm [Install Helm](https://helm.sh/docs/intro/install) before beginning. The [Helm chart][helm] is the recommended way o... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/installation.mdx | main | vault | [
0.06028267368674278,
0.027290603145956993,
-0.0027021626010537148,
-0.05188971385359764,
-0.01774083450436592,
-0.011912927031517029,
-0.10562601685523987,
-0.0062373303808271885,
0.02051233872771263,
0.02191053330898285,
0.01963067054748535,
-0.039941199123859406,
0.005239803344011307,
0.... | 0.045095 |
the Helm chart uses to cleanup resources and remove finalizers on the uninstall path. Please see [`config/samples`](https://github.com/hashicorp/vault-secrets-operator/tree/main/config/samples) or `config/samples` in the downloaded release artifacts for additional resources. ## Upgrade using Kustomize Upgrading using K... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/installation.mdx | main | vault | [
0.04859153926372528,
0.08559087663888931,
0.03734296187758446,
-0.08427713811397552,
0.014152209274470806,
-0.04330095648765564,
-0.1325116753578186,
0.026503203436732292,
-0.004904245492070913,
0.01403125375509262,
0.04404373839497566,
-0.012246961705386639,
-0.032961469143629074,
-0.0436... | 0.03603 |
# Use protected secrets in Kubernetes with CSI @include 'alerts/enterprise-only.mdx' While the Vault Secrets Operator lets you store Vault secrets in clusters as native Kubernetes Secrets, you must install the Vault Secrets Operator [CSI driver](https://github.com/container-storage-interface/spec/blob/master/spec.md) t... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/csi/index.mdx | main | vault | [
0.03162631765007973,
0.030622979626059532,
-0.023731499910354614,
-0.021055230870842934,
0.007465464062988758,
-0.010843693278729916,
-0.004138478543609381,
0.007179467473179102,
0.09389609843492508,
0.029051290825009346,
0.0024750486481934786,
-0.013968193903565407,
0.05596896633505821,
-... | 0.111888 |
# Set up the Vault Secrets Operator CSI driver @include 'alerts/enterprise-only.mdx' Use the Vault Secrets Operator CSI driver with a `CSISecrets` resource to allow authorized Pods to mount ephemeral volumes containing secrets from Vault as indexed files. Indexing starts at `0` and represents the associated position in... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/csi/setup.mdx | main | vault | [
0.023024728521704674,
-0.015369769185781479,
-0.07063406705856323,
-0.015121723525226116,
-0.018668003380298615,
-0.02807515114545822,
0.004814609419554472,
0.008593421429395676,
0.05466100573539734,
-0.015614868141710758,
0.00977681390941143,
-0.007629635743796825,
0.07969220727682114,
0.... | 0.117256 |
the CSISecrets resource To securely sync secrets between Vault and your application Pods, you must create a custom resource called `CSISecrets` that lists information available to the CSI driver Pods. For example, the following resource definition creates a single `CSISecrets` resource that can: - Generate secret IDs f... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/csi/setup.mdx | main | vault | [
-0.00414279056712985,
0.020291823893785477,
-0.07296808809041977,
-0.0019271837081760168,
-0.022521991282701492,
-0.03225688263773918,
0.007938183844089508,
0.036040350794792175,
0.03501264750957489,
-0.029693661257624626,
0.028326554223895073,
-0.08403573930263519,
0.07578690350055695,
0.... | 0.080459 |
# Troubleshooting the Vault Secrets Operator CSI driver ## Driver not appearing in cluster Verify that you have enabled it with the `csi.enabled` field on the Vault Secrets Operator Helm chart. You can do this by either adding the field to your `values.yaml` file, or by passing it directly with the `--set` flag: ```she... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/csi/troubleshooting.mdx | main | vault | [
0.09743182361125946,
-0.015850454568862915,
-0.010927902534604073,
-0.05271809175610542,
0.01784244365990162,
-0.030014611780643463,
-0.07047851383686066,
0.017847035080194473,
0.05020381510257721,
0.03710518777370453,
0.05221296846866608,
-0.050275690853595734,
0.044515009969472885,
0.075... | 0.042455 |
secret ID for subsequent logins to Vault, you have to set up the [AppRole auth method](/vault/docs/auth/approle) in Vault ahead of time. If you see errors when logging into Vault with your secret ID, verify the following: - If using response-wrapping, the wrapping token's TTL has not expired. - If using response-wrappi... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/csi/troubleshooting.mdx | main | vault | [
-0.015775218605995178,
0.04896777868270874,
-0.025384623557329178,
-0.004262784030288458,
0.006917533930391073,
-0.07492155581712723,
-0.03463400900363922,
0.031160244718194008,
0.05233107879757881,
-0.0159438569098711,
0.03127548471093178,
-0.00343437516130507,
0.05502820387482643,
0.0753... | -0.04172 |
@include '../../../global/partials/alerts/hvs-eof-notice.mdx' # Vault Secrets Operator with HCP Vault Secrets The Vault secrets operator (VSO) syncs your [HCP Vault Secrets app](/hcp/docs/vault-secrets) (HVSA) to a Kubernetes Secret. Vault syncs each `HCPVaultSecretsApp` custom resource periodically to ensure that chan... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/hvs.mdx | main | vault | [
0.009272292256355286,
0.06490551680326462,
0.02908376045525074,
-0.068011574447155,
-0.0011578104458749294,
0.03840356320142746,
-0.01631893217563629,
-0.012267704121768475,
0.05166212469339371,
-0.03724263608455658,
-0.006973791867494583,
-0.041245173662900925,
0.06490252166986465,
-0.061... | 0.09968 |
@include 'vso/common-links.mdx' # Vault Secrets Operator The Vault Secrets Operator (VSO) supports Vault as a secret source, which lets you seamlessly integrate VSO with a Vault instance running on any platform. The Vault Secrets Operator (VSO) is a fully supported component of HashiCorp Vault. ## Supported Vault platf... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/index.mdx | main | vault | [
-0.02121025137603283,
0.030340176075696945,
-0.04953055828809738,
-0.055144403129816055,
0.012719860300421715,
-0.025780804455280304,
-0.11162595450878143,
-0.003623134223744273,
-0.02480694092810154,
-0.07615968585014343,
0.011926627717912197,
0.013353333808481693,
0.07708676159381866,
-0... | 0.049852 |
configuration that can be inherited by multiple `VaultAuth` custom resources. It supports multiple authentication methods and allows you to define a default authentication method that can be overridden by individual VaultAuth custom resources. See `vaultAuthGlobalRef` in the [VaultAuth spec][va-spec] for more details. ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/index.mdx | main | vault | [
0.001698015257716179,
0.024575937539339066,
-0.04530387371778488,
-0.038103558123111725,
-0.07272715866565704,
-0.015953760594129562,
0.014073665253818035,
-0.010086036287248135,
0.08936953544616699,
-0.04383065551519394,
-0.07387761026620865,
-0.04808581620454788,
0.06873302906751633,
0.0... | 0.044625 |
of `VaultPKISecret` custom resource. Please consult [PKI Secrets Engine - Setup and Usage](/vault/docs/secrets/pki/setup) for configuring PKI secrets engine. The following results in a request to `http://127.0.0.1:8200/v1/pki/issue/default` to generate TLS certificates. ```yaml --- apiVersion: secrets.hashicorp.com/v1b... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/index.mdx | main | vault | [
-0.02016514725983143,
0.059705134481191635,
-0.03632079064846039,
0.008348103612661362,
-0.05565556511282921,
-0.0737469270825386,
-0.03766618296504021,
-0.0281200110912323,
0.08596702665090561,
-0.03812561184167862,
0.013635634444653988,
-0.06656455248594284,
0.04265907034277916,
0.041112... | 0.000916 |
# Instant updates for a VaultStaticSecret Vault Secrets Operator (VSO) supports instant updates for [VaultStaticSecrets][vss-spec] by subscribing to event notifications from Vault. ## Before you start - \*\*You must have [Vault Secrets Operator](/vault/docs/platform/k8s/vso/sources/vault) installed\*\*. - \*\*You must ... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/instant-updates.mdx | main | vault | [
0.03926480561494827,
0.03189817816019058,
-0.03426874428987503,
-0.011745331808924675,
-0.01745857670903206,
-0.03982812538743019,
-0.028778577223420143,
-0.024589508771896362,
0.049454059451818466,
-0.01696810871362686,
-0.01433658879250288,
-0.059055015444755554,
0.02655797265470028,
0.0... | -0.000725 |
# Persist and encrypt the Vault client cache By default, the [Vault client cache](/vault/docs/platform/k8s/vso/sources/vault#vault-client-cache) does not persist. You can use the [transit secrets engine](/vault/docs/secrets/transit) with Vault Secrets Operator (VSO) to store and encrypt the client cache in your Vault s... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/client-cache.mdx | main | vault | [
-0.01601538434624672,
0.04092656075954437,
0.0009393416694365442,
0.024676088243722916,
-0.0668763518333435,
-0.0029911191668361425,
-0.08201499283313751,
-0.016423342749476433,
0.0874573141336441,
0.0019303434528410435,
-0.017321281135082245,
0.01947150193154812,
0.000049394617235520855,
... | -0.010316 |
vault-secrets-operator \ -n vault-secrets-operator ``` The pod in the operator deployment restarts once the `VSO\_CLIENT\_CACHE\_PERSISTENCE\_MODEL` environment variable persists. ## Optional: Verify client cache storage and encryption 1. Confirm the Vault Secrets Operator logs the following information on startup: ```... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/client-cache.mdx | main | vault | [
0.019304834306240082,
0.056358594447374344,
-0.029074816033244133,
0.014644704759120941,
-0.033834733068943024,
-0.062081433832645416,
-0.006086514797061682,
-0.018031850457191467,
0.08215170353651047,
-0.014412994496524334,
0.00036562271998263896,
0.020748749375343323,
-0.001294649206101894... | -0.008914 |
# GCP auth support for Vault Secrets Operator The Vault Secrets Operator (VSO) supports authenticating to Vault's [GCP auth](/vault/docs/auth/gcp) method, using Google's Kubernetes Engine (GKE) workload identity. 1. Follow Google's [Use Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-... | https://github.com/hashicorp/web-unified-docs/blob/main/content/vault/v1.21.x/content/docs/deploy/kubernetes/vso/sources/vault/auth/gcp.mdx | main | vault | [
-0.0252939872443676,
0.03648599609732628,
0.036397144198417664,
-0.06834954023361206,
-0.07215742766857147,
-0.001099016284570098,
0.043994106352329254,
-0.01056936290115118,
0.061236850917339325,
0.005999821703881025,
-0.020166026428341866,
-0.08444464951753616,
0.0649719089269638,
0.0089... | -0.001097 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.