Skip to content

Commit 85b3798

Browse files
committed
Add information about setting an operator image pull secret (jenkins-ignore)
1 parent a663fa3 commit 85b3798

File tree

2 files changed

+30
-1
lines changed

2 files changed

+30
-1
lines changed

docs-source/content/security/secrets.md

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ description: "Kubernetes secrets for the WebLogic operator"
88
#### Contents
99
* [WebLogic domain credentials secret](#weblogic-domain-credentials-secret)
1010
* [WebLogic domain image pull secret](#weblogic-domain-image-pull-secret)
11+
* [WebLogic operator image pull secret](#weblogic-operator-image-pull-secret)
1112
* [WebLogic operator configuration override secrets](#weblogic-operator-configuration-override-secrets)
1213
* [WebLogic operator external REST interface secret](#weblogic-operator-external-rest-interface-secret)
1314
* [WebLogic operator internal REST interface secret](#weblogic-operator-internal-rest-interface-secret)
@@ -71,14 +72,36 @@ username: 8 bytes
7172
#### WebLogic domain image pull secret
7273

7374
The WebLogic domain that the operator manages can have images that are protected
74-
in the registry. The `imagePullSecrets` setting can be used to specify the
75+
in the registry. The `imagePullSecrets` setting on the `Domain` can be used to specify the
7576
Kubernetes `Secret` that holds the registry credentials.
7677

7778
{{% notice info %}}
7879
For more information, see [Docker Image Protection]({{<relref "/security/domain-security/image-protection.md#weblogic-domain-in-docker-image-protection">}})
7980
under **Domain security**.
8081
{{% /notice %}}
8182

83+
#### WebLogic operator image pull secret
84+
85+
The helm chart for installing the operator has an option to specify the
86+
image pull secret used for the operator's image when using a private registry.
87+
The Kubernetes `Sercret` of type `docker-registry` should be created in the namespace
88+
where the operator is deployed.
89+
90+
Here is an example of using the `helm install` command to set the image name and image pull secret:
91+
```bash
92+
$ helm install kubernetes/charts/weblogic-operator \
93+
--set "image=my.io/my-operator-image:1.0" \
94+
--set "imagePullSecrets[0].name=my-operator-image-pull-secret" \
95+
--name my-weblogic-operator --namespace weblogic-operator-ns \
96+
--wait
97+
```
98+
99+
{{% notice info %}}
100+
For more information, see
101+
[Install the operator Helm chart]({{<relref "/userguide/managing-operators/installation/_index.md#install-the-operator-helm-chart">}})
102+
under **User Guide**.
103+
{{% /notice %}}
104+
82105
#### WebLogic operator configuration override secrets
83106

84107
The WebLogic operator supports embedding macros within configuration override templates

docs-source/content/userguide/managing-operators/installation/_index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,12 @@ If `weblogic-operator-namespace` exists, then it will be used. If it does not e
4040

4141
You can verify the operator installation by examining the output from the `helm install` command.
4242

43+
{{% notice note %}}
44+
When the operator image is stored in a private registry, see
45+
[WebLogic operator image pull secret]({{<relref "/security/secrets.md#weblogic-operator-image-pull-secret">}})
46+
for more information on specifying the registry credentials.
47+
{{% /notice %}}
48+
4349
#### Alternatively, install the operator Helm chart from GitHub chart repository
4450

4551
Add this repository to the Helm installation:

0 commit comments

Comments
 (0)