1. Deploying and Managing Oracle Access Management on Kubernetes
  2. Installing Oracle Access Management on Kubernetes
  3. Creating Oracle Access Management Domains
  4. Creating OAM Domains Using WLST Offline Scripts
  5. Verifying the WLST OAM Deployment

7.1.9 Verifying the WLST OAM Deployment

Verifying the domain, pods and services

Verify the domain, servers pods and services are created and in the READY state with a status of 1/1, by running the following command:
kubectl get all,domains -n <domain_namespace>
For example:
kubectl get all,domains -n oamns
The output will look similar to the following:
NAME                                                 READY   STATUS      RESTARTS   AGE
pod/accessdomain-adminserver                         1/1     Running     0          11m
pod/accessdomain-create-oam-infra-domain-job-7c9r9   0/1     Completed   0          18m
pod/accessdomain-oam-policy-mgr1                     1/1     Running     0          3m31s
pod/accessdomain-oam-server1                         1/1     Running     0          3m31s

NAME                                          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)     AGE
service/accessdomain-adminserver              ClusterIP   None            <none>        7001/TCP    11m
service/accessdomain-cluster-oam-cluster      ClusterIP   10.101.59.154   <none>        14100/TCP   3m31s
service/accessdomain-cluster-policy-cluster   ClusterIP   10.98.236.51    <none>        15100/TCP   3m31s
service/accessdomain-oam-policy-mgr1          ClusterIP   None            <none>        15100/TCP   3m31s
service/accessdomain-oam-policy-mgr2          ClusterIP   10.104.92.12    <none>        15100/TCP   3m31s
service/accessdomain-oam-policy-mgr3          ClusterIP   10.96.244.37    <none>        15100/TCP   3m31s
service/accessdomain-oam-policy-mgr4          ClusterIP   10.105.201.23   <none>        15100/TCP   3m31s
service/accessdomain-oam-policy-mgr5          ClusterIP   10.110.12.227   <none>        15100/TCP   3m31s
service/accessdomain-oam-server1              ClusterIP   None            <none>        14100/TCP   3m31s
service/accessdomain-oam-server2              ClusterIP   10.96.137.33    <none>        14100/TCP   3m31s
service/accessdomain-oam-server3              ClusterIP   10.103.178.35   <none>        14100/TCP   3m31s
service/accessdomain-oam-server4              ClusterIP   10.97.254.78    <none>        14100/TCP   3m31s
service/accessdomain-oam-server5              ClusterIP   10.105.65.104   <none>        14100/TCP   3m31s

NAME                                                 COMPLETIONS   DURATION   AGE
job.batch/accessdomain-create-oam-infra-domain-job   1/1           2m6s       18m

NAME                                  AGE
domain.weblogic.oracle/accessdomain   12m
   
NAME                                                  AGE
cluster.weblogic.oracle/accessdomain-oam-cluster      11m
cluster.weblogic.oracle/accessdomain-policy-cluster   11m

Note:

It will take several minutes before all the services listed above show. When a pod has a STATUS of 0/1 the pod is started but the OAM server associated with it is currently starting. While the pods are starting you can check the startup status in the pod logs, by running the following command:
kubectl logs <pod> -n <namespace>
For example:
kubectl logs accessdomain-adminserver -n accessdomain-adminserver
The default domain created by the script has the following characteristics:
  • An Administration Server named AdminServer listening on port 7001.
  • A configured OAM cluster named oam_cluster of size 5.
  • A configured Policy Manager cluster named policy_cluster of size 5.
  • One started OAM Managed Server, named oam_server1, listening on port 14100.
  • One started Policy Manager Managed Servers named oam-policy-mgr1, listening on port 15100.
  • Log files that are located in <persistent_volume>/logs/<domainUID>.

Verifying the Domain

Run the following command to describe the domain:
kubectl describe domain <domain_uid> -n <domain_namespace>
For example:
kubectl describe domain accessdomain -n oamns
The output will look similar to the following:
Name:         accessdomain
Namespace:    oamns
Labels:       weblogic.domainUID=accessdomain
Annotations:  <none>
API Version:  weblogic.oracle/v9
Kind:         Domain
Metadata:
  Creation Timestamp:  <DATE>
  Generation:          1
  Managed Fields:
    API Version:  weblogic.oracle/v9
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
        f:labels:
          .:
          f:weblogic.domainUID:
      f:spec:
        .:
        f:adminServer:
          .:
          f:adminChannelPortForwardingEnabled:
          f:serverPod:
            .:
            f:env:
          f:serverStartPolicy:
        f:clusters:
        f:dataHome:
        f:domainHome:
        f:domainHomeSourceType:
        f:failureRetryIntervalSeconds:
        f:failureRetryLimitMinutes:
        f:httpAccessLogInLogHome:
        f:image:
        f:imagePullPolicy:
        f:imagePullSecrets:
        f:includeServerOutInPodLog:
        f:logHome:
        f:logHomeEnabled:
        f:logHomeLayout:
        f:maxClusterConcurrentShutdown:
        f:maxClusterConcurrentStartup:
        f:maxClusterUnavailable:
        f:replicas:
        f:serverPod:
          .:
          f:env:
          f:volumeMounts:
          f:volumes:
        f:serverStartPolicy:
        f:webLogicCredentialsSecret:
          .:
          f:name:
    Manager:      kubectl-client-side-apply
    Operation:    Update
    Time:         <DATE>
    API Version:  weblogic.oracle/v9
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:clusters:
        f:conditions:
        f:observedGeneration:
        f:servers:
        f:startTime:
    Manager:         Kubernetes Java Client
    Operation:       Update
    Subresource:     status
    Time:            <DATE>
  Resource Version:  2074089
  UID:               e194d483-7383-4359-adb9-bf97de36518b
Spec:
  Admin Server:
    Admin Channel Port Forwarding Enabled:  true
    Server Pod:
      Env:
        Name:             USER_MEM_ARGS
        Value:            -Djava.security.egd=file:/dev/./urandom -Xms512m -Xmx1024m
        Name:             CLASSPATH
        Value:            /u01/oracle/wlserver/server/lib/weblogic.jar
    Server Start Policy:  IfNeeded
  Clusters:
    Name:                          accessdomain-oam-cluster
    Name:                          accessdomain-policy-cluster
  Data Home:
  Domain Home:                     /u01/oracle/user_projects/domains/accessdomain
  Domain Home Source Type:         PersistentVolume
  Failure Retry Interval Seconds:  120
  Failure Retry Limit Minutes:     1440
  Http Access Log In Log Home:     true
  Image:                           container-registry.oracle.com/middleware/oam_cpu:12.2.1.4-jdk8-ol8-<January'25>
  Image Pull Policy:               IfNotPresent
  Image Pull Secrets:
    Name:                           orclcred
  Include Server Out In Pod Log:    true
  Log Home:                         /u01/oracle/user_projects/domains/logs/accessdomain
  Log Home Enabled:                 true
  Log Home Layout:                  ByServers
  Max Cluster Concurrent Shutdown:  1
  Max Cluster Concurrent Startup:   0
  Max Cluster Unavailable:          1
  Replicas:                         1
  Server Pod:
    Env:
      Name:   JAVA_OPTIONS
      Value:  -Dweblogic.StdoutDebugEnabled=false
      Name:   USER_MEM_ARGS
      Value:  -Djava.security.egd=file:/dev/./urandom -Xms256m -Xmx1024m
    Volume Mounts:
      Mount Path:  /u01/oracle/user_projects/domains
      Name:        weblogic-domain-storage-volume
    Volumes:
      Name:  weblogic-domain-storage-volume
      Persistent Volume Claim:
        Claim Name:     accessdomain-domain-pvc
  Server Start Policy:  IfNeeded
  Web Logic Credentials Secret:
    Name:  accessdomain-credentials
Status:
  Clusters:
    Cluster Name:  oam_cluster
    Conditions:
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Available
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Completed
    Label Selector:          weblogic.domainUID=accessdomain,weblogic.clusterName=oam_cluster
    Maximum Replicas:        5
    Minimum Replicas:        0
    Observed Generation:     1
    Ready Replicas:          1
    Replicas:                1
    Replicas Goal:           1
    Cluster Name:            policy_cluster
    Conditions:
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Available
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Completed
    Label Selector:          weblogic.domainUID=accessdomain,weblogic.clusterName=policy_cluster
    Maximum Replicas:        5
    Minimum Replicas:        0
    Observed Generation:     1
    Ready Replicas:          1
    Replicas:                1
    Replicas Goal:           1
  Conditions:
    Last Transition Time:  <DATE>
    Status:                True
    Type:                  Available
    Last Transition Time:  <DATE>
    Status:                True
    Type:                  Completed
  Observed Generation:     1
  Servers:
    Health:
      Activation Time:  <DATE>
      Overall Health:   ok
      Subsystems:
        Subsystem Name:  ServerRuntime
        Symptoms:
    Node Name:     worker-node2
    Pod Phase:     Running
    Pod Ready:     True
    Server Name:   AdminServer
    State:         RUNNING
    State Goal:    RUNNING
    Cluster Name:  oam_cluster
    Health:
      Activation Time:  <DATE>
      Overall Health:   ok
      Subsystems:
        Subsystem Name:  ServerRuntime
       Symptoms:
    Node Name:     worker-node1
    Pod Phase:     Running
    Pod Ready:     True
    Server Name:   oam_server1
    State:         RUNNING
    State Goal:    RUNNING
    Cluster Name:  oam_cluster
    Server Name:   oam_server2
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oam_cluster
    Server Name:   oam_server3
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oam_cluster
    Server Name:   oam_server4
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oam_cluster
    Server Name:   oam_server5
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  policy_cluster
    Health:
      Activation Time:  <DATE>
      Overall Health:   ok
      Subsystems:
        Subsystem Name:  ServerRuntime
        Symptoms:
    Node Name:     worker-node1
    Pod Phase:     Running
    Pod Ready:     True
    Server Name:   oam_policy_mgr1
    State:         RUNNING
    State Goal:    RUNNING
    Cluster Name:  policy_cluster
    Server Name:   oam_policy_mgr2
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  policy_cluster
    Server Name:   oam_policy_mgr3
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  policy_cluster
    Server Name:   oam_policy_mgr4
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  policy_cluster
    Server Name:   oam_policy_mgr5
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
  Start Time:      <DATE>
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Created    15m    weblogic.operator  Domain accessdomain was created.
  Normal  Available  2m56s  weblogic.operator  Domain accessdomain is available: a sufficient number of its servers have reached the ready state.
  Normal  Completed  2m56s  weblogic.operator  Domain accessdomain is complete because all of the following are true: there is no failure detected, there are no pending server shutdowns, and all servers expected to be running are ready and at their target image, auxiliary images, restart version, and introspect version.
In the Status section of the output, the available servers and clusters are listed.

Verifying the Pods

Run the following command to view the pods and the nodes they are running on:
kubectl get pods -n <domain_namespace> -o wide
For example:
kubectl get pods -n oamns -o wide
The output will look similar to the following:
NAME                                            READY   STATUS      RESTARTS   AGE     IP            NODE             NOMINATED NODE   READINESS GATES
accessdomain-adminserver                         1/1     Running     0          18m   10.244.6.63   10.250.42.252   <none>           <none>
accessdomain-create-oam-infra-domain-job-7c9r9   0/1     Completed   0          25m   10.244.6.61   10.250.42.252   <none>           <none>
accessdomain-oam-policy-mgr1                     1/1     Running     0          10m   10.244.5.13   10.250.42.255   <none>           <none>
accessdomain-oam-server1                         1/1     Running     0          10m   10.244.5.12   10.250.42.255   <none>           <none>

Configuring the Ingress

If the domain deploys successfully, and all the above checks are verified, you are ready to configure the Ingress. See, Configuring Ingress.