mirror of
https://github.com/external-secrets/external-secrets.git
synced 2024-12-14 11:57:59 +00:00
7416a84b2a
* added new crd-names flag to reconcile only installed CRDs in cert controller Signed-off-by: Steven Bressey <sbressey@bressey.me> * add guide to disable cluster features Signed-off-by: Steven Bressey <sbressey@bressey.me> * fix fmt Signed-off-by: Steven Bressey <sbressey@bressey.me> Co-authored-by: Steven Bressey <sbressey@bressey.me>
21 lines
1,011 B
Markdown
21 lines
1,011 B
Markdown
# Deploying without ClusterSecretStore and ClusterExternalSecret
|
|
|
|
When deploying External Secrets Operator via Helm chart, the default configuration will install `ClusterSecretStore` and `ClusterExternalSecret` CRDs and these objects will be processed by the operator.
|
|
|
|
In order to disable both or one of these features, it is necessary to configure the `crds.*` Helm value, as well as the `process*` Helm value, as these 2 values are connected.
|
|
|
|
If you would like to install the operator without `ClusterSecretStore` and `ClusterExternalSecret` management, you will have to :
|
|
|
|
* set `crds.createClusterExternalSecret` to false
|
|
* set `crds.createClusterSecretStore` to false
|
|
* set `processClusterExternalSecret` to false
|
|
* set `processClusterStore` to false
|
|
|
|
Example:
|
|
|
|
```bash
|
|
helm install external-secrets external-secrets/external-secrets --set crds.createClusterExternalSecret=false \
|
|
--set crds.createClusterSecretStore=false \
|
|
--set processClusterExternalSecret=false \
|
|
--set processClusterStore=false
|
|
```
|