|
|
@@ -2181,7 +2181,7 @@ If you want to design cross-namespace SecretStores you must use <a href="../clus
|
|
|
<span class="w"> </span><span class="c1"># You can specify retry settings for the http connection</span>
|
|
|
<span class="w"> </span><span class="c1"># these fields allow you to set a maxRetries before failure, and</span>
|
|
|
<span class="w"> </span><span class="c1"># an interval between the retries.</span>
|
|
|
-<span class="w"> </span><span class="c1"># Current supported providers: AWS, IBM</span>
|
|
|
+<span class="w"> </span><span class="c1"># Current supported providers: AWS, Hashicorp Vault, IBM</span>
|
|
|
<span class="w"> </span><span class="nt">retrySettings</span><span class="p">:</span>
|
|
|
<span class="w"> </span><span class="nt">maxRetries</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">5</span>
|
|
|
<span class="w"> </span><span class="nt">retryInterval</span><span class="p">:</span><span class="w"> </span><span class="s">"10s"</span>
|
|
|
@@ -2209,6 +2209,7 @@ If you want to design cross-namespace SecretStores you must use <a href="../clus
|
|
|
<span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">awssm-secret</span>
|
|
|
<span class="w"> </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">secret-access-key</span>
|
|
|
|
|
|
+<span class="w"> </span><span class="c1"># (2) Hashicorp Vault</span>
|
|
|
<span class="w"> </span><span class="nt">vault</span><span class="p">:</span>
|
|
|
<span class="w"> </span><span class="nt">server</span><span class="p">:</span><span class="w"> </span><span class="s">"https://vault.acme.org"</span>
|
|
|
<span class="w"> </span><span class="c1"># Path is the mount path of the Vault KV backend endpoint</span>
|
|
|
@@ -2256,7 +2257,7 @@ If you want to design cross-namespace SecretStores you must use <a href="../clus
|
|
|
<span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="s">"my-secret"</span>
|
|
|
<span class="w"> </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="s">"vault"</span>
|
|
|
|
|
|
-<span class="w"> </span><span class="c1"># (2): GCP Secret Manager</span>
|
|
|
+<span class="w"> </span><span class="c1"># (3): GCP Secret Manager</span>
|
|
|
<span class="w"> </span><span class="nt">gcpsm</span><span class="p">:</span>
|
|
|
<span class="w"> </span><span class="c1"># Auth defines the information necessary to authenticate against GCP by getting</span>
|
|
|
<span class="w"> </span><span class="c1"># the credentials from an already created Kubernetes Secret.</span>
|