Deployment of a WebLogic Server in Kubernetes Using the WebLogic Kubernetes Operator.
To build the Kubernetes cluster locally we will use Docker and minikube.
k3d cluster create wls-operator# Check the nodes of Local K8s Cluster.
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k3d-wlc-operator-server-0 Ready control-plane,master 45m v1.30.3+k3s1 172.18.0.2 <none> K3s v1.30.3+k3s1 6.5.0-41-generic containerd://1.7.17-k3s1
Establish Helm configuration by indicating the location of the operator's Helm chart as follows.
helm repo add weblogic-operator https://oracle.github.io/weblogic-kubernetes-operator/charts --force-updateThe Kubernetes system differentiates between user accounts and service accounts due to several considerations. The primary differentiation is that user accounts are intended for human users, whereas service accounts are designed for processes operating within pods. Service accounts are also a requirement for the operator. When a service account isn't explicitly stated, it will automatically use the default service account of the namespace. If there's a need to utilize a different service account, it's mandatory to establish both the operator's namespace and the service account prior to deploying the operator's Helm chart.
- Therefore, you should pre-create the operator's namespace.
kubectl create namespace weblogic-operator-ns-local
# Check if the namespace created successfully
kubectl get ns- Also, create and the service account:
kubectl -n weblogic-operator-ns-local create serviceaccount weblogic-operator-sa-local
# Check if the service account created successfully
kubectl -n weblogic-operator-ns-local get saInstall the operator using helm.
helm install weblogic-operator weblogic-operator/weblogic-operator \
--namespace weblogic-operator-ns-local \
--set "serviceAccount=weblogic-operator-sa-local" \
--set "enableClusterRoleBinding=true" \
--set "domainNamespaceSelectionStrategy=LabelSelector" \
--set "domainNamespaceLabelSelector=weblogic-operator\=enabled" \
--waitNOTE: For OpenShift (CRC) : --set "kubernetesPlatform=OpenShift"
helm install weblogic-operator weblogic-operator/weblogic-operator \
--namespace weblogic-operator-ns-local \
--set "serviceAccount=weblogic-operator-sa-local" \
--set "enableClusterRoleBinding=true" \
--set "domainNamespaceSelectionStrategy=LabelSelector" \
--set "domainNamespaceLabelSelector=weblogic-operator\=enabled" \
--set "kubernetesPlatform=OpenShift" \
--wait
The output will be similar to the following:
NAME: sample-weblogic-operator
LAST DEPLOYED: Thu Aug 8 12:05:56 2024
NAMESPACE: sample-weblogic-operator-ns
STATUS: deployed
REVISION: 1
TEST SUITE: NoneConfirm the operator's pod is operational by enumerating the pods in the operator's specific namespace. There should be two visible pods - one for the operator itself and another for the conversion webhook. The conversion webhook is a unique deployment in your Kubernetes cluster that seamlessly performs automatic upgrades to domain resources.
kubectl -n weblogic-operator-ns-local get podsValidate the operator's running status by examining the pod's log.
kubectl -n weblogic-operator-ns-local logs -c weblogic-operator deployments/weblogic-operatorThe output will be similar to the following:
$ kubectl -n weblogic-operator-ns-local logs -c weblogic-operator deployments/weblogic-operator
Launching Oracle WebLogic Server Kubernetes Operator...
VM settings:
Max. Heap Size (Estimated): 9.45G
Using VM: Java HotSpot(TM) 64-Bit Server VM
{"timestamp":"2024-08-08T14:07:14.495044792Z","thread":1,"fiber":"","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.helpers.HealthCheckHelper","method":"createAndValidateKubernetesVersion","timeInMillis":1723126034495,"message":"Kubernetes version is: v1.30.3+k3s1","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:14.605003727Z","thread":1,"fiber":"","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain$MainDelegateImpl","method":"logStartup","timeInMillis":1723126034605,"message":"Oracle WebLogic Kubernetes Operator, version: 4.2.5, implementation: 1469541cfe267182b44bf54b3d86157cba63a946.1469541, build time: 2024-07-26T19:19:38+0000","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:14.608055329Z","thread":1,"fiber":"","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain$MainDelegateImpl","method":"lambda$logStartup$0","timeInMillis":1723126034608,"message":"The following optional operator features are enabled: []","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:14.6106433Z","thread":1,"fiber":"","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain$MainDelegateImpl","method":"logStartup","timeInMillis":1723126034610,"message":"Operator namespace is: weblogic-operator-ns-local","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:14.612269599Z","thread":1,"fiber":"","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain$MainDelegateImpl","method":"logStartup","timeInMillis":1723126034612,"message":"Operator service account is: weblogic-operator-sa-local","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:15.22076161Z","thread":71,"fiber":"-fiber-1 NOT_COMPLETE","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain$ReadResponseStep","method":"onSuccess","timeInMillis":1723126035220,"message":"The Custom Resource Definition (CRD) for domains.weblogic.oracle is not installed, waiting for 10 seconds for the CRD to be installed.","exception":"","code":"","headers":{},"body":""}
{"timestamp":"2024-08-08T14:07:25.645064316Z","thread":85,"fiber":"fiber-1 NOT_COMPLETE","namespace":"","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.OperatorMain","method":"logStartingLivenessMessage","timeInMillis":1723126045645,"message":"Starting operator liveness Thread","exception":"","code":"","headers":{},"body":""}
- Establish and assign a label to a namespace capable of hosting one or multiple domains.
# Create ns
kubectl create namespace wls-test-domain-ns
# Label ns
kubectl label ns wls-test-domain-ns weblogic-operator=enabledConfirm the creation of namespace with proper labels.
kubectl get ns --show-labels-
Confirm your acceptance of the WebLogic Server images license agreement.
- Navigate to the Oracle Container Registry (OCR)using any web browser and authenticate yourself using the Oracle Single Sign-On (SSO) service. If you don't have an SSO account, click on the 'Sign In' button located on the top right corner of the webpage to create one.
- Input 'weblogic' into the search bar and choose 'weblogic' from the results that appear.
- Use the drop-down menu to select the language of your preference, and then proceed by clicking on the 'Continue' button.
- Review and agree to the terms and conditions of the license agreement.
-
Initiate a docker-registry secret to enable the download of the example WebLogic Server image from the registry.
kubectl create secret docker-registry weblogic-repo-credentials \
--docker-server=container-registry.oracle.com \
--docker-username='[email protected]' \
--docker-password='********' \
--docker-email='[email protected]' \
-n wls-test-domain-nsReplace the docker-username, docker-email & docker-password with YOUR details for access the registry.
Choose a username and password for the WebLogic domain administrator. Then, use these credentials to create a Kubernetes Secret for the domain.
kubectl -n wls-test-domain-ns create secret generic wls-test-domain-weblogic-credentials \
--from-literal=username='weblogic' --from-literal=password='welcome1'Set up an encryption secret for the runtime domain.
kubectl -n wls-test-domain-ns create secret generic \
wls-test-domain-runtime-encryption-secret \
--from-literal=password='weblogic1'Establish the wls-test-domain domain resource along with its associated wls-test-domain-cluster-1 cluster resource by employing a singular YAML resource file that outlines both resources. Instead of replacing the conventional WebLogic configuration files, the domain and cluster resources work in conjunction with them to articulate the Kubernetes artifacts related to the respective domain.
kubectl apply -f domain-resource.yamlVerify that the operator has initiated the servers for the domain.
kubectl -n wls-test-domain-ns describe domain wls-test-domainThe status of the domain can be obtained using this command.
kubectl -n wls-test-domain-ns get domain wls-test-domain -o jsonpath='{.status}'Shortly, you will observe the Administration Server and Managed Servers are in active state.
kubectl -n wls-test-domain-ns get pods
# Output
$ kubectl -n wls-test-domain-ns get pods
NAME READY STATUS RESTARTS AGE
wls-test-domain-admin-server 1/1 Running 0 37m
wls-test-domain-managed-server1 1/1 Running 0 37mIn addition, all the Kubernetes Services associated with the domain should be discernible.
kubectl -n wls-test-domain-ns get svc
# Output will be like the following:
$ kubectl -n wls-test-domain-ns get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
wls-test-domain-admin-server ClusterIP None <none> 7001/TCP 106s
wls-test-domain-cluster-cluster-1 ClusterIP 10.43.248.94 <none> 8001/TCP 71s
wls-test-domain-managed-server1 ClusterIP None <none> 8001/TCP 71s
Formulate an ingress pathway for the specific domain within the corresponding domain namespace, utilizing the subsequent YAML file.
kubectl create namespace traefik
helm install traefik-operator traefik/traefik \
--namespace traefik \
--set "ports.web.nodePort=30305" \
--set "ports.websecure.nodePort=30443" \
--set "kubernetes.namespaces={traefik}"
helm upgrade traefik-operator traefik/traefik \
--namespace traefik \
--reuse-values \
--set "kubernetes.namespaces={traefik,wls-test-domain-ns}"
kubectl -n wls-test-domain-ns apply -f ingress-route.yaml
kubectl get svc -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP,9153/TCP 27m
metrics-server ClusterIP 10.43.51.120 <none> 443/TCP 27m
traefik LoadBalancer 10.43.202.52 172.19.0.2 80:31776/TCP,443:32202/TCP 26m
Browser:
Welcome to the WebLogic on Kubernetes Quick Start Sample
WebLogic Server Name: managed-server1 Pod Name: wls-test-domain-managed-server1 Current time: 13:31:53
By default, when you create a service of type LoadBalancer in a Kubernetes cluster, it's the responsibility of the cloud provider's network infrastructure to provision a network load balancer and to create routes so that the service can be accessed via the external IP address of the load balancer.
This allows you to run and test services locally in an environment that is more similar to a full-scale, hosted Kubernetes environment.
If you want to delete the cluster entirely, including all data and state, you can use the following command.
k3d cluster delete wls-operator