1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/external-secrets-operator-install-console.adoc
2026-01-06 17:15:30 +00:00

54 lines
2.0 KiB
Plaintext

// Module included in the following assemblies:
//
// * security/external_secrets_operator/external-secrets-operator-install.adoc
:_mod-docs-content-type: PROCEDURE
[id="external-secrets-operator-install-console_{context}"]
= Installing the {external-secrets-operator} by using the web console
[role="_abstract"]
Install the {external-secrets-operator} by using the web console to add secret management features to your cluster. By doing this task, you can select an update channel and approval strategy to ensure the Operator stays current.
.Prerequisites
* You have access to the cluster with `cluster-admin` privileges.
* You have access to the {product-title} web console.
.Procedure
. Log in to the {product-title} web console.
. Navigate to *Ecosystem* -> *Software Catalog*.
. Enter *{external-secrets-operator-short}* in the search box.
. Select the *{external-secrets-operator}* from the generated list and click *Install*.
. On the *Install Operator* page:
.. Update the *Update channel*, if necessary. The channel defaults to *stable-v1*, which installs the latest stable release of the {external-secrets-operator-short}.
.. Select the version from *Version* drop-down list.
.. Choose the *Installed Namespace* for the Operator.
+
* To use the default Operator namespace, select the *Operator recommended Namespace* option.
+
* To use the namespace that you created, select the *Select a Namespace* option, and then select the namespace from the drop-down list.
+
* If the default `external-secrets-operator` namespace does not exist, it is created for you by the {olm-first}.
+
.. Select an *Update approval* strategy.
+
* The *Automatic* strategy enables {olm} to automatically update the Operator when a new version is available.
+
* The *Manual* strategy requires a user with appropriate credentials to approve the Operator update.
.. Click *Install*.
.Verification
. Navigate to *Ecosystem* -> *Installed Operators*.
. Verify that *{external-secrets-operator-short}* is listed with a *Status* of *Succeeded* in the `external-secrets-operator` namespace.