The operator uses Helm to create the necessary resources and then deploy the operator in a Kubernetes cluster. This document describes how to install, upgrade, and uninstall the operator.
You can find the operator image in GitHub Container Registry.
helm install command to install the operator Helm chart. As part of this, you must specify a “release” name for the operator.
You can override default configuration values in the chart by doing one of the following:
--valueoption on the Helm command line.
You supply the
–-namespace argument from the
helm install command line to specify the namespace in which the operator will be installed. If not specified, then it defaults to
default. If the namespace does not already exist, then Helm will automatically create it (and create a default service account in the new namespace), but will not remove it when the release is uninstalled. If the namespace already exists, then Helm will use it. These are standard Helm behaviors.
Similarly, you may override the default
serviceAccount configuration value to specify a service account in the operator’s namespace, the operator will use. If not specified, then it defaults to
default (for example, the namespace’s default service account). If you want to use a different service account, then you must create the operator’s namespace and the service account before installing the operator Helm chart.
For example, using Helm 3.x:
$ kubectl create namespace weblogic-operator-namespace
$ helm install weblogic-operator kubernetes/charts/weblogic-operator \ --namespace weblogic-operator-namespace \ --values custom-values.yaml --wait
$ helm install weblogic-operator kubernetes/charts/weblogic-operator \ --namespace weblogic-operator-namespace \ --set "javaLoggingLevel=FINE" --wait
This creates a Helm release, named
weblogic-operator in the
weblogic-operator-namespace namespace, and configures a deployment and supporting resources for the operator.
You can verify the operator installation by examining the output from the
helm install command.
For more information on specifying the registry credentials when the operator image is stored in a private registry, see Operator image pull secret.
Add this repository to the Helm installation:
$ helm repo add weblogic-operator https://oracle.github.io/weblogic-kubernetes-operator/charts --force-update
Verify that the repository was added correctly:
$ helm repo list
NAME URL weblogic-operator https://oracle.github.io/weblogic-kubernetes-operator/charts
Install the operator from the repository:
$ helm install weblogic-operator weblogic-operator/weblogic-operator
Because operator 3.0.0 introduces non-backward compatible changes, you cannot use
helm upgrade to upgrade
a 2.6.0 operator to a 3.x operator. Instead, you must delete the 2.6.0 operator and then install the
The deletion of the 2.6.0 operator will not affect the Domain CustomResourceDefinition (CRD) and will not stop any WebLogic Server instances already running.
When the 3.x operator is installed, it will automatically roll any running WebLogic Server instances created by the 2.6.0 operator. This rolling restart will preserve WebLogic cluster availability guarantees (for clustered members only) similarly to any other rolling restart.
To delete the 2.6.0 operator:
$ helm delete weblogic-operator -n weblogic-operator-namespace
Then install the 3.x operator using the installation instructions above.
The following instructions will be applicable to upgrade operators within the 3.x release family as additional versions are released.
To upgrade the operator, use the
helm upgrade command. Make sure that the
weblogic-kubernetes-operator repository on your local machine is at the
operator release to which you are upgrading. When upgrading the operator,
helm upgrade command requires that you supply a new Helm chart and image. For example:
$ helm upgrade \ --reuse-values \ --set image=ghcr.io/oracle/weblogic-kubernetes-operator:3.3.2 \ --namespace weblogic-operator-namespace \ --wait \ weblogic-operator \ kubernetes/charts/weblogic-operator
helm uninstall command is used to remove an operator release and its associated resources from the Kubernetes cluster. The release name used with the
helm uninstall command is the same release name used with the
helm install command (see Install the Helm chart). For example:
$ helm uninstall weblogic-operator -n weblogic-operator-namespace
If the operator’s namespace did not exist before the Helm chart was installed, then Helm will create it, however,
helm uninstall will not remove it.
After removing the operator deployment, you should also remove the Domain custom resource definition (CRD):
$ kubectl delete customresourcedefinition domains.weblogic.oracle
Note that the Domain custom resource definition is shared. Do not delete the CRD if there are other operators in the same cluster.