Check the Health of a Load Balancer

Learn how to view the status of a load balancers associated with the instance's Kubernetes cluster managed by Oracle WebLogic Server for OKE.

1. Access the administration compute instance for your domain.
   See Access the Administration Instance.
2. Run the following command:

   kubectl get services --all-namespaces

   Sample output of services:

   NAMESPACE                 NAME                                   TYPE           CLUSTER-IP      EXTERNAL-IP       PORT(S)                      AGE
   default                   kubernetes                             ClusterIP      10.96.0.1       <none>            443/TCP                      27h
   wlsoke-ingress-nginx      okename-internal                       LoadBalancer   10.96.185.81    100.121.170.271   80:32144/TCP                 27h
   jenkins-ns                jenkins-service                        ClusterIP      10.96.121.100   <none>            8080/TCP,50000/TCP           27h
   kube-system               kube-dns                               ClusterIP      10.96.7.5       <none>            53/UDP,53/TCP,9153/TCP       27h
   kube-system               tiller-deploy                          ClusterIP      10.96.76.135    <none>            44134/TCP                    27h
   okename-domain-ns         mydomain-cluster-okename-cluster       ClusterIP      10.96.143.98    <none>            8001/TCP                     27h
   okename-domain-ns         mydomain-okename-adminserver           ClusterIP      None            <none>            30012/TCP,7001/TCP           27h
   okename-domain-ns         mydomain-okename-managed-server1       ClusterIP      None            <none>            8001/TCP                     27h
   okename-domain-ns         mydomain-okename-managed-server2       ClusterIP      None            <none>            8001/TCP                     27h
   wlsoke-ingress-nginx      mydomain-lb-external                   LoadBalancer   10.96.162.263   144.25.10.101     80:32148/TCP,443:31808/TCP   27h
   okename-operator-ns       internal-weblogic-operator-svc         ClusterIP      10.96.92.254    <none>            8082/TCP                     27h

   Sample output of services when Verrazzano is enabled:

   NAMESPACE        NAME                                         TYPE         CLUSTER-IP     EXTERNAL-IP      PORT(S)                                    AGE
   cattle-system    rancher                                              ClusterIP     10.96.233.56    <none>          80/TCP,443/TCP                             27h
   cattle-system    rancher-webhook                                      ClusterIP     10.96.46.145    <none>          443/TCP                                    27h
   cert-manager     cert-manager                                         ClusterIP     10.96.17.222    <none>          9402/TCP                                   27h
   cert-manager     cert-manager-webhook                                 ClusterIP     10.96.237.157   <none>          443/TCP                                    27h
   default          kubernetes                                           ClusterIP     10.96.0.1       <none>          443/TCP                                    27h
   fleet-system     gitjob                                               ClusterIP     10.96.195.224   <none>          80/TCP                                     27h
   ingress-nginx    ingress-controller-ingress-nginx-controller          LoadBalancer  10.96.220.49    10.0.5.242      443:32231/TCP                              27h
   ingress-nginx    ingress-controller-ingress-nginx-controller-metrics  ClusterIP     10.96.60.166    <none>          10254/TCP                                  27h
   ingress-nginx    ingress-controller-ingress-nginx-defaultbackend      ClusterIP     10.96.154.132   <none>          80/TCP                                     27h
   istio-system     istio-egressgateway                                  ClusterIP     10.96.255.249   <none>          80/TCP,443/TCP                             27h
   istio-system     istio-ingressgateway                                 LoadBalancer  10.96.47.34     129.80.253.214  15021:32050/TCP,80:31611/TCP,443:30082/TCP 27h

   Make a note of the IP address of the services with type LoadBalancer and in the EXTERNAL-IP column.

3. Disconnect from the administration compute instance.
4. Sign in to the Oracle Cloud Infrastructure Console.
5. Click the navigation menu and select Networking > Load Balancers.
6. Select the Compartment that contains your stack.
7. Find the required load balancer by searching with the IP addresses that you noted in Step2.
8. Click the name of the load balance against the IP address you searched for.
9. Under Resources on the left, click Metrics.

   The Metrics tab displays a default set of charts for the selected load balancer.