Skip to content

Latest commit

 

History

History
93 lines (83 loc) · 3.46 KB

03-wls-operator.md

File metadata and controls

93 lines (83 loc) · 3.46 KB

Installing the WebLogic Server Kubernetes Operator

We depend on the WebLogic Server Kubernetes Operator to create and manage WebLogic domains. For detailed installation information, see Install the Operator.

In this example, we provide the steps to install the operator 2.3.0 release.

Pulling the Images

We need two images, the WebLogic Server Kubernetes Operator image from Docker Hub and the WebLogic Server image from the Oracle Container Registry. Before pulling the image, you must:

  • Acquire a user account to the image sites.
    If you do not already have Oracle Single Sign-On credentials, go to https://container-registry.oracle.com and create them by clicking the Sign In link at the top of the page.
  • Log in to the site in your browser, find the image, and accept the license.

Pull the WebLogic Sever Kubernetes Operator 2.3.0 image.

docker login
docker pull oracle/weblogic-kubernetes-operator:2.3.0

Pull the WebLogic Server 12.2.1.3 image.

docker login container-registry.oracle.com
docker pull container-registry.oracle.com/middleware/weblogic:12.2.1.3

Verify that the WebLogic image has the right patch set.

docker run container-registry.oracle.com/middleware/weblogic:12.2.1.3  sh -c '$ORACLE_HOME/OPatch/opatch lspatches'

output

29135930;One-off
27117282;One-off
26355633;One-off
26287183;One-off
26261906;One-off
26051289;One-off

OPatch succeeded.

Confirm that patch set 29135930 is in the patch list.

Installing the WebLogic Server Kubernetes Operator

Create a namespace in which to run the operator.

kubectl create namespace weblogic-operator1

Create a service account.

kubectl create serviceaccount -n weblogic-operator1 sample-weblogic-operator-sa

Add the operator chart repository to Helm.

helm repo add weblogic-operator https://oracle.github.io/weblogic-kubernetes-operator/charts

Install the operator with the operator chart with version 2.3.0.

helm install weblogic-operator/weblogic-operator \
  --version 2.3.0 \
  --name weblogic-operator \
  --namespace weblogic-operator1 \
  --set serviceAccount=sample-weblogic-operator-sa \
  --set image=oracle/weblogic-kubernetes-operator:2.3.0 \
  --set "domainNamespaces={default}" \
  --wait

Verification

Wait until the operator pod is running and ready.

kubectl -n weblogic-operator1 get pod

output

NAME                                READY   STATUS    RESTARTS   AGE
weblogic-operator-fcfff877c-c4972   1/1     Running   0          30h

Wait until the domain CRD is registered successfully.

kubectl get crd domains.weblogic.oracle

output

NAME                      CREATED AT
domains.weblogic.oracle   2019-05-28T07:17:26Z

Verify that the domain CRD version is correct.

kubectl get crd domains.weblogic.oracle -o jsonpath="{.spec.version}"

The expected version should be v5. Because the operator is backward compatible, a domain resource with any version older than v5 should be supported.

Now the WebLogic Server Kubernetes Operator is running and it's monitoring the default namespace. Later we'll deploy a domain resource to the default namespace and the operator will be responsible for creating, running, and managing the WebLogic domain.

Next: Running a WebLogic Domain