mirror of
https://github.com/external-secrets/external-secrets.git
synced 2024-12-14 11:57:59 +00:00
Merge pull request #536 from external-secrets/feat/add-olm-install-release-docs
docs: add OLM docs
This commit is contained in:
paul-the-alien[bot]
GitHub
commit
93483832a1
4 changed files with 688 additions and 5 deletions
|
|
@ -8,8 +8,9 @@ The external-secrets project is released on a as-needed basis. Feel free to open
|
|||
|
||||
1. Run `Create Release` Action to create a new release, pass in the desired version number to release.
|
||||
2. GitHub Release, Changelog will be created by the `release.yml` workflow which also promotes the container image.
|
||||
3. (optional) update Helm Chart
|
||||
4. Announce the new release in the `#external-secrets` Kubernetes Slack
|
||||
3. update Helm Chart, see below
|
||||
4. update OLM bundle, see [helm-operator docs](https://github.com/external-secrets/external-secrets-helm-operator/blob/main/docs/release.md#operatorhubio)
|
||||
5. Announce the new release in the `#external-secrets` Kubernetes Slack
|
||||
|
||||
## Release Helm Chart
|
||||
|
||||
|
|
|
|||
|
|
@ -77,6 +77,10 @@ Events: <none>
|
|||
For more advanced examples, please read the other
|
||||
[guides](guides-introduction.md).
|
||||
|
||||
## Installing with OLM
|
||||
|
||||
External-secrets can be managed by [Operator Lifecycle Manager](https://olm.operatorframework.io/) (OLM) via an installer operator. It is made available through [OperatorHub.io](https://operatorhub.io/), this installation method is suited best for OpenShift. See installation instructions on the [external-secrets-operator](https://operatorhub.io/operator/external-secrets-operator) package.
|
||||
|
||||
## Uninstalling
|
||||
|
||||
Before continuing, ensure that all external-secret resources that have been created by users have been deleted.
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ lifecycle of the secrets for you.
|
|||
To get started, please read through [API overview](api-overview.md) this should
|
||||
give you a high-level overview to understand the API and use-cases. After that
|
||||
please follow one of our [guides](guides-introduction.md) to get a jump start
|
||||
using the operator.
|
||||
using the operator. See our [getting started guide](guides-getting-started.md) for installation instructions.
|
||||
|
||||
For a complete reference of the API types please refer to our [API
|
||||
Reference](spec.md).
|
||||
|
|
|
|||
682
docs/spec.md
682
docs/spec.md
|
|
@ -225,6 +225,282 @@ see: <a href="https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.
|
|||
</td>
|
||||
</tr></tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AkeylessAuth">AkeylessAuth
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.AkeylessProvider">AkeylessProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>secretRef</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AkeylessAuthSecretRef">
|
||||
AkeylessAuthSecretRef
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AkeylessAuthSecretRef">AkeylessAuthSecretRef
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.AkeylessAuth">AkeylessAuth</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AkeylessAuthSecretRef
|
||||
AKEYLESS_ACCESS_TYPE_PARAM: AZURE_OBJ_ID OR GCP_AUDIENCE OR ACCESS_KEY OR KUB_CONFIG_NAME.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>accessID</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The SecretAccessID is used for authentication</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>accessType</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>accessTypeParam</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AkeylessProvider">AkeylessProvider
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreProvider">SecretStoreProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AkeylessProvider Configures an store to sync secrets using Akeyless KV.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>akeylessGWApiURL</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>Akeyless GW API Url from which the secrets to be fetched from.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>authSecretRef</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AkeylessAuth">
|
||||
AkeylessAuth
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>Auth configures how the operator authenticates with Akeyless.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AlibabaAuth">AlibabaAuth
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.AlibabaProvider">AlibabaProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AlibabaAuth contains a secretRef for credentials.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>secretRef</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AlibabaAuthSecretRef">
|
||||
AlibabaAuthSecretRef
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AlibabaAuthSecretRef">AlibabaAuthSecretRef
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.AlibabaAuth">AlibabaAuth</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AlibabaAuthSecretRef holds secret references for Alibaba credentials.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>accessKeyIDSecretRef</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The AccessKeyID is used for authentication</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>accessKeySecretSecretRef</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The AccessKeySecret is used for authentication</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AlibabaProvider">AlibabaProvider
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreProvider">SecretStoreProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AlibabaProvider configures a store to sync secrets using the Alibaba Secret Manager provider.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>auth</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AlibabaAuth">
|
||||
AlibabaAuth
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>endpoint</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>regionID</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>Alibaba Region to be used for the provider</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AuthType">AuthType
|
||||
(<code>string</code> alias)</p></h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.AzureKVProvider">AzureKVProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>AuthType describes how to authenticate to the Azure Keyvault
|
||||
Only one of the following auth types may be specified.
|
||||
If none of the following auth type is specified, the default one
|
||||
is ServicePrincipal.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Value</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr><td><p>"ManagedIdentity"</p></td>
|
||||
<td><p>Using Managed Identity to authenticate. Used with aad-pod-identity instelled in the clister.</p>
|
||||
</td>
|
||||
</tr><tr><td><p>"ServicePrincipal"</p></td>
|
||||
<td><p>Using service principal to authenticate, which needs a tenantId, a clientId and a clientSecret.</p>
|
||||
</td>
|
||||
</tr></tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.AzureKVAuth">AzureKVAuth
|
||||
</h3>
|
||||
<p>
|
||||
|
|
@ -285,6 +561,23 @@ github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
|||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>authType</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AuthType">
|
||||
AuthType
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Auth type defines how to authenticate to the keyvault service.
|
||||
Valid values are:
|
||||
- “ServicePrincipal” (default): Using a service principal (tenantId, clientId, clientSecret)
|
||||
- “ManagedIdentity”: Using Managed Identity assigned to the pod (see aad-pod-identity)</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>vaultUrl</code></br>
|
||||
<em>
|
||||
string
|
||||
|
|
@ -302,7 +595,8 @@ string
|
|||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>TenantID configures the Azure Tenant to send requests to.</p>
|
||||
<em>(Optional)</em>
|
||||
<p>TenantID configures the Azure Tenant to send requests to. Required for ServicePrincipal auth type.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
|
@ -315,11 +609,110 @@ AzureKVAuth
|
|||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>Auth configures how the operator authenticates with Azure.</p>
|
||||
<em>(Optional)</em>
|
||||
<p>Auth configures how the operator authenticates with Azure. Required for ServicePrincipal auth type.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>identityId</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>If multiple Managed Identity is assigned to the pod, you can select the one to be used</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.CAProvider">CAProvider
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.VaultProvider">VaultProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>Defines a location to fetch the cert for the vault provider from.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>type</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.CAProviderType">
|
||||
CAProviderType
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The type of provider to use such as “Secret”, or “ConfigMap”.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>name</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The name of the object located at the provider type.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>key</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The key the value inside of the provider type to use, only used with “Secret” type</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>namespace</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The namespace the Provider type is in.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.CAProviderType">CAProviderType
|
||||
(<code>string</code> alias)</p></h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.CAProvider">CAProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Value</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr><td><p>"ConfigMap"</p></td>
|
||||
<td></td>
|
||||
</tr><tr><td><p>"Secret"</p></td>
|
||||
<td></td>
|
||||
</tr></tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.ClusterSecretStore">ClusterSecretStore
|
||||
</h3>
|
||||
<p>
|
||||
|
|
@ -386,6 +779,20 @@ SecretStoreProvider
|
|||
<p>Used to configure the provider. Only one provider may be set</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>retrySettings</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreRetrySettings">
|
||||
SecretStoreRetrySettings
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Used to configure http retries if failed</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
|
|
@ -953,6 +1360,18 @@ ExternalSecretTemplate
|
|||
<p>Template defines a blueprint for the created Secret resource.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>immutable</code></br>
|
||||
<em>
|
||||
bool
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Immutable defines if the final secret will be immutable</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.ExternalSecretTemplate">ExternalSecretTemplate
|
||||
|
|
@ -1393,6 +1812,143 @@ string
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.OracleAuth">OracleAuth
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.OracleProvider">OracleProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>secretRef</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.OracleSecretRef">
|
||||
OracleSecretRef
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>SecretRef to pass through sensitive information.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.OracleProvider">OracleProvider
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreProvider">SecretStoreProvider</a>)
|
||||
</p>
|
||||
<p>
|
||||
<p>Configures an store to sync secrets using a Oracle Vault
|
||||
backend.</p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>auth</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.OracleAuth">
|
||||
OracleAuth
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>Auth configures how secret-manager authenticates with the Oracle Vault.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>user</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>User is an access OCID specific to the account.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>tenancy</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>projectID is an access token specific to the secret.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>region</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>projectID is an access token specific to the secret.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.OracleSecretRef">OracleSecretRef
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.OracleAuth">OracleAuth</a>)
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>privatekey</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>The Access Token is used for authentication</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>fingerprint</code></br>
|
||||
<em>
|
||||
github.com/external-secrets/external-secrets/apis/meta/v1.SecretKeySelector
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<p>projectID is an access token specific to the secret.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.SecretStore">SecretStore
|
||||
</h3>
|
||||
<p>
|
||||
|
|
@ -1459,6 +2015,20 @@ SecretStoreProvider
|
|||
<p>Used to configure the provider. Only one provider may be set</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>retrySettings</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreRetrySettings">
|
||||
SecretStoreRetrySettings
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Used to configure http retries if failed</p>
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
</td>
|
||||
</tr>
|
||||
|
|
@ -1542,6 +2112,20 @@ AzureKVProvider
|
|||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>akeyless</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AkeylessProvider">
|
||||
AkeylessProvider
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Akeyless configures this store to sync secrets using Akeyless Vault provider</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>vault</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.VaultProvider">
|
||||
|
|
@ -1570,6 +2154,20 @@ GCPSMProvider
|
|||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>oracle</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.OracleProvider">
|
||||
OracleProvider
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Oracle configures this store to sync secrets using Oracle Vault provider</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>ibm</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.IBMProvider">
|
||||
|
|
@ -1610,6 +2208,20 @@ GitlabProvider
|
|||
<p>GItlab configures this store to sync secrets using Gitlab Variables provider</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>alibaba</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.AlibabaProvider">
|
||||
AlibabaProvider
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Alibaba configures this store to sync secrets using Alibaba Cloud provider</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.SecretStoreRef">SecretStoreRef
|
||||
|
|
@ -1655,6 +2267,44 @@ Defaults to <code>SecretStore</code></p>
|
|||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.SecretStoreRetrySettings">SecretStoreRetrySettings
|
||||
</h3>
|
||||
<p>
|
||||
(<em>Appears on:</em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreSpec">SecretStoreSpec</a>)
|
||||
</p>
|
||||
<p>
|
||||
</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Field</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>
|
||||
<code>maxRetries</code></br>
|
||||
<em>
|
||||
int32
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>retryInterval</code></br>
|
||||
<em>
|
||||
string
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.SecretStoreSpec">SecretStoreSpec
|
||||
</h3>
|
||||
<p>
|
||||
|
|
@ -1699,6 +2349,20 @@ SecretStoreProvider
|
|||
<p>Used to configure the provider. Only one provider may be set</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>retrySettings</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.SecretStoreRetrySettings">
|
||||
SecretStoreRetrySettings
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>Used to configure http retries if failed</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.SecretStoreStatus">SecretStoreStatus
|
||||
|
|
@ -2416,6 +3080,20 @@ plain HTTP protocol connection. If not set the system root certificates
|
|||
are used to validate the TLS connection.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
<code>caProvider</code></br>
|
||||
<em>
|
||||
<a href="#external-secrets.io/v1alpha1.CAProvider">
|
||||
CAProvider
|
||||
</a>
|
||||
</em>
|
||||
</td>
|
||||
<td>
|
||||
<em>(Optional)</em>
|
||||
<p>The provider for the CA bundle to use to validate Vault server certificate.</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="external-secrets.io/v1alpha1.YandexLockboxAuth">YandexLockboxAuth
|
||||
|
|
|
|||
Loading…
Reference in a new issue