1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/eso-external-secrets-manager.adoc
2025-11-26 19:43:48 +00:00

51 lines
1.5 KiB
Plaintext

// Module included in the following assemblies:
//
// * security/external_secrets_operator/external-secrets-operator-api.adoc
:_mod-docs-content-type: REFERENCE
[id="eso-external-secrets-manager_{context}"]
= externalSecretsManager
[role="_abstract"]
The `externalSecretsManager` object defines the configuration and information of deployments managed by the {external-secrets-operator-short}. Set the name to `cluster` as this allows only one instance of `externalSecretsManager` per cluster.
You can configure global options by using `externalSecretsManager`. This serves as a centralized configuration for managing multiple controllers of the Operator. The Operator automatically creates the `externalSecretsManager` object during installation.
[cols="1,1,1,1,1",options="header"]
|===
| Field
| Type
| Description
| Default
| Validation
| `apiVersion`
| _string_
| The `apiVersion` specifies the version of the schema in use, which is `operator.openshift.io/v1alpha1`.
|
|
| `kind`
| _string_
| `kind` specifies the type of the object, which is `externalSecretsManager` for this Object.
|
|
| `metadata`
| link:https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.31/#objectmeta-v1-meta[_ObjectMeta_]
| Refer to Kubernetes API documentation for details about the `metadata` fields.
|
|
| `spec`
| _object_
| `spec` contains specifications of the desired behavior.
|
|
| `status`
| _object_
| `status` displays the most recently observed state of the controllers in the {external-secrets-operator-short}.
|
|
|===