a. Create OIG domains using WLST scripts

  1. Introduction

  2. Prerequisites

  3. Prepare the create domain script

  4. Run the create domain script

    a. Generate the create domain script

    b. Setting the OIM server memory parameters

    c. Run the create domain scripts

  5. Verify the results

    a. Verify the domain, pods and services

    b. Verify the domain

    c. Verify the pods

Introduction

The OIG deployment scripts demonstrate the creation of an OIG domain home on an existing Kubernetes persistent volume (PV) and persistent volume claim (PVC). The scripts also generate the domain YAML file, which can then be used to start the Kubernetes artifacts of the corresponding domain.

Note: If you want to create the OIG domain using WDT models, skip the steps below and go to Create OIG Domains Using WDT Models.

Prerequisites

Before you begin, perform the following steps:

  1. Review the Domain resource documentation.
  2. Ensure that you have executed all the preliminary steps documented in Prepare your environment.
  3. Ensure that the database is up and running.

Prepare the create domain script

The sample scripts for Oracle Identity Governance domain deployment are available at $WORKDIR/kubernetes/create-oim-domain.

  1. Make a copy of the create-domain-inputs.yaml file:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv
$ cp create-domain-inputs.yaml create-domain-inputs.yaml.orig

  2. Edit the create-domain-inputs.yaml and modify the following parameters. Save the file when complete:

    Note: Do not edit any other parameters other than ones mentioned below.

    domainUID: <domain_uid>
domainHome: /u01/oracle/user_projects/domains/<domain_uid>
image: <image_name>
imagePullSecretName: <container_registry_secret>
weblogicCredentialsSecretName: <kubernetes_domain_secret>
logHome: /u01/oracle/user_projects/domains/logs/<domain_id>
namespace: <domain_namespace>
persistentVolumeClaimName: <pvc_name>
rcuSchemaPrefix: <rcu_prefix>
rcuDatabaseURL: <rcu_db_host>:<rcu_db_port>/<rcu_db_service_name>
rcuCredentialsSecret: <kubernetes_rcu_secret>
frontEndHost: <front_end_hostname>
frontEndPort: <front_end_port>

    For example:

    domainUID: governancedomain
domainHome: /u01/oracle/user_projects/domains/governancedomain
image: container-registry.oracle.com/middleware/oig_cpu:12.2.1.4-jdk8-ol8-<April'24>
imagePullSecretName: orclcred
weblogicCredentialsSecretName: oig-domain-credentials
logHome: /u01/oracle/user_projects/domains/logs/governancedomain
namespace: oigns
persistentVolumeClaimName: governancedomain-domain-pvc
rcuSchemaPrefix: OIGK8S
rcuDatabaseURL: mydatabasehost.example.com:1521/orcl.example.com
rcuCredentialsSecret: oig-rcu-credentials
frontEndHost: example.com
frontEndPort: 14100

    Note: For now frontEndHost and front_end_port should be set to example.com and 14100 respectively. These values will be changed to the correct values in post installation tasks in Set OIMFrontendURL using MBeans.

A full list of parameters in the create-domain-inputs.yaml file are shown below:

Parameter Definition Default
adminPort Port number for the Administration Server inside the Kubernetes cluster. 7001
adminNodePort Port number of the Administration Server outside the Kubernetes cluster. 30701
adminServerName Name of the Administration Server. AdminServer
clusterName Name of the WebLogic cluster instance to generate for the domain. By default the cluster name is oimcluster for the OIG domain. oimcluster
configuredManagedServerCount Number of Managed Server instances to generate for the domain. 5
createDomainFilesDir Directory on the host machine to locate all the files to create a WebLogic domain, including the script that is specified in the createDomainScriptName property. By default, this directory is set to the relative path wlst, and the create script will use the built-in WLST offline scripts in the wlst directory to create the WebLogic domain. It can also be set to the relative path wdt, and then the built-in WDT scripts will be used instead. An absolute path is also supported to point to an arbitrary directory in the file system. The built-in scripts can be replaced by the user-provided scripts or model files as long as those files are in the specified directory. Files in this directory are put into a Kubernetes config map, which in turn is mounted to the createDomainScriptsMountPath, so that the Kubernetes pod can use the scripts and supporting files to create a domain home. wlst
createDomainScriptsMountPath Mount path where the create domain scripts are located inside a pod. The create-domain.sh script creates a Kubernetes job to run the script (specified in the createDomainScriptName property) in a Kubernetes pod to create a domain home. Files in the createDomainFilesDir directory are mounted to this location in the pod, so that the Kubernetes pod can use the scripts and supporting files to create a domain home. /u01/weblogic
createDomainScriptName Script that the create domain script uses to create a WebLogic domain. The create-domain.sh script creates a Kubernetes job to run this script to create a domain home. The script is located in the in-pod directory that is specified in the createDomainScriptsMountPath property. If you need to provide your own scripts to create the domain home, instead of using the built-it scripts, you must use this property to set the name of the script that you want the create domain job to run. create-domain-job.sh
domainHome Home directory of the OIG domain. If not specified, the value is derived from the domainUID as /shared/domains/<domainUID>. /u01/oracle/user_projects/domains/oimcluster
domainPVMountPath Mount path of the domain persistent volume. /u01/oracle/user_projects/domains
domainUID Unique ID that will be used to identify this particular domain. Used as the name of the generated WebLogic domain as well as the name of the Kubernetes domain resource. This ID must be unique across all domains in a Kubernetes cluster. This ID cannot contain any character that is not valid in a Kubernetes service name. oimcluster
exposeAdminNodePort Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. false
exposeAdminT3Channel Boolean indicating if the T3 administrative channel is exposed outside the Kubernetes cluster. true
image OIG container image. The operator requires OIG 12.2.1.4. Refer to OIG domains for details on how to obtain or create the image. oracle/oig:12.2.1.4.0
imagePullPolicy WebLogic container image pull policy. Legal values are IfNotPresent, Always, or Never IfNotPresent
imagePullSecretName Name of the Kubernetes secret to access the container registry to pull the OIG container image. The presence of the secret will be validated when this parameter is specified.
includeServerOutInPodLog Boolean indicating whether to include the server .out to the pod’s stdout. true
initialManagedServerReplicas Number of Managed Servers to initially start for the domain. 2
javaOptions Java options for starting the Administration Server and Managed Servers. A Java option can have references to one or more of the following pre-defined variables to obtain WebLogic domain information: $(DOMAIN_NAME), $(DOMAIN_HOME), $(ADMIN_NAME), $(ADMIN_PORT), and $(SERVER_NAME). -Dweblogic.StdoutDebugEnabled=false
logHome The in-pod location for the domain log, server logs, server out, and Node Manager log files. If not specified, the value is derived from the domainUID as /shared/logs/<domainUID>. /u01/oracle/user_projects/domains/logs/oimcluster
managedServerNameBase Base string used to generate Managed Server names. oim_server
managedServerPort Port number for each Managed Server. 8001
namespace Kubernetes namespace in which to create the domain. oimcluster
persistentVolumeClaimName Name of the persistent volume claim created to host the domain home. If not specified, the value is derived from the domainUID as <domainUID>-weblogic-sample-pvc. oimcluster-domain-pvc
productionModeEnabled Boolean indicating if production mode is enabled for the domain. true
serverStartPolicy Determines which WebLogic Server instances will be started. Legal values are Never, IfNeeded, AdminOnly. IfNeeded
t3ChannelPort Port for the T3 channel of the NetworkAccessPoint. 30012
t3PublicAddress Public address for the T3 channel. This should be set to the public address of the Kubernetes cluster. This would typically be a load balancer address. For development environments only: In a single server (all-in-one) Kubernetes deployment, this may be set to the address of the master, or at the very least, it must be set to the address of one of the worker nodes. If not provided, the script will attempt to set it to the IP address of the Kubernetes cluster
weblogicCredentialsSecretName Name of the Kubernetes secret for the Administration Server’s user name and password. If not specified, then the value is derived from the domainUID as <domainUID>-weblogic-credentials. oimcluster-domain-credentials
weblogicImagePullSecretName Name of the Kubernetes secret for the container registry, used to pull the WebLogic Server image.
serverPodCpuRequest, serverPodMemoryRequest, serverPodCpuCLimit, serverPodMemoryLimit The maximum amount of compute resources allowed, and minimum amount of compute resources required, for each server pod. Please refer to the Kubernetes documentation on Managing Compute Resources for Containers for details. Resource requests and resource limits are not specified.
rcuSchemaPrefix The schema prefix to use in the database, for example OIGK8S. You may wish to make this the same as the domainUID in order to simplify matching domains to their RCU schemas. OIGK8S
rcuDatabaseURL The database URL. oracle-db.default.svc.cluster.local:1521/devpdb.k8s
rcuCredentialsSecret The Kubernetes secret containing the database credentials. oimcluster-rcu-credentials
frontEndHost The entry point URL for the OIM. Not set
frontEndPort The entry point port for the OIM. Not set
datasourceType Type of JDBC datasource applicable for the OIG domain. Legal values are agl and generic. Choose agl for Active GridLink datasource and generic for Generic datasource. For enterprise deployments, Oracle recommends that you use GridLink data sources to connect to Oracle RAC databases. See the Enterprise Deployment Guide for further details. generic

Note that the names of the Kubernetes resources in the generated YAML files may be formed with the value of some of the properties specified in the create-inputs.yaml file. Those properties include the adminServerName, clusterName and managedServerNameBase. If those values contain any characters that are invalid in a Kubernetes service name, those characters are converted to valid values in the generated YAML files. For example, an uppercase letter is converted to a lowercase letter and an underscore ("_") is converted to a hyphen ("-").

The sample demonstrates how to create an OIG domain home and associated Kubernetes resources for a domain that has one cluster only. In addition, the sample provides the capability for users to supply their own scripts to create the domain home for other use cases. The generated domain YAML file could also be modified to cover more use cases.

Run the create domain script

Generate the create domain script

  1. Run the create domain script, specifying your inputs file and an output directory to store the generated artifacts:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv
$ mkdir output
$ ./create-domain.sh -i create-domain-inputs.yaml -o /<path to output-directory>

    For example:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv
$ mkdir output
$ ./create-domain.sh -i create-domain-inputs.yaml -o output

    The output will look similar to the following:

    Input parameters being used
export version="create-weblogic-sample-domain-inputs-v1"
export adminPort="7001"
export adminServerName="AdminServer"
export domainUID="governancedomain"
export domainHome="/u01/oracle/user_projects/domains/governancedomain"
export serverStartPolicy="IfNeeded"
export clusterName="oim_cluster"
export configuredManagedServerCount="5"
export initialManagedServerReplicas="1"
export managedServerNameBase="oim_server"
export managedServerPort="14000"
export image="container-registry.oracle.com/middleware/oig_cpu:12.2.1.4-jdk8-ol8-<April'24>"
export imagePullPolicy="IfNotPresent"
export imagePullSecretName="orclcred"
export productionModeEnabled="true"
export weblogicCredentialsSecretName="oig-domain-credentials"
export includeServerOutInPodLog="true"
export logHome="/u01/oracle/user_projects/domains/logs/governancedomain"
export t3ChannelPort="30012"
export exposeAdminT3Channel="false"
export adminNodePort="30701"
export exposeAdminNodePort="false"
export namespace="oigns"
javaOptions=-Dweblogic.StdoutDebugEnabled=false
export persistentVolumeClaimName="governancedomain-domain-pvc"
export domainPVMountPath="/u01/oracle/user_projects/domains"
export createDomainScriptsMountPath="/u01/weblogic"
export createDomainScriptName="create-domain-job.sh"
export createDomainFilesDir="wlst"
export rcuSchemaPrefix="OIGK8S"
export rcuDatabaseURL="mydatabasehost.example.com:1521/orcl.example.com"
export rcuCredentialsSecret="oig-rcu-credentials"
export frontEndHost="example.com"
export frontEndPort="14100"
export datasourceType="generic"

validateWlsDomainName called with governancedomain
createFiles - valuesInputFile is create-domain-inputs.yaml
createDomainScriptName is create-domain-job.sh
Generating output/weblogic-domains/governancedomain/create-domain-job.yaml
Generating output/weblogic-domains/governancedomain/delete-domain-job.yaml
Generating output/weblogic-domains/governancedomain/domain.yaml
Checking to see if the secret governancedomain-domain-credentials exists in namespace oigns
configmap/governancedomain-create-fmw-infra-sample-domain-job-cm created
Checking the configmap governancedomain-create-fmw-infra-sample-domain-job-cm was created
configmap/governancedomain-create-fmw-infra-sample-domain-job-cm labeled
Checking if object type job with name governancedomain-create-fmw-infra-sample-domain-job exists
No resources found in oigns namespace.
Creating the domain by creating the job output/weblogic-domains/governancedomain/create-domain-job.yaml
job.batch/governancedomain-create-fmw-infra-sample-domain-job created
Waiting for the job to complete...
status on iteration 1 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 2 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 3 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 4 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 5 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 6 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 7 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 8 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 9 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 10 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Running
status on iteration 11 of 40
pod governancedomain-create-fmw-infra-sample-domain-job-8cww8 status is Completed

Domain governancedomain was created and will be started by the WebLogic Kubernetes Operator

The following files were generated:
  output/weblogic-domains/governancedomain/create-domain-inputs.yaml
  output/weblogic-domains/governancedomain/create-domain-job.yaml
  output/weblogic-domains/governancedomain/domain.yaml
sed

Completed
$

    Note: If the create domain script creation fails, refer to the Troubleshooting section.

Setting the OIM server memory parameters

  1. Navigate to the /output/weblogic-domains/<domain_uid> directory:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv/output/weblogic-domains/<domain_uid>

    For example:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv/output/weblogic-domains/governancedomain

  2. Edit the domain.yaml and locate the section of the file starting with: - clusterName: oim_cluster under governancedomain-oim-cluster. Add the following lines:

    serverPod:
 env:
 - name: USER_MEM_ARGS
   value: "-Djava.security.egd=file:/dev/./urandom -Xms2408m -Xmx8192m
 resources:
   limits:
     cpu: "2"
     memory: "8Gi"
   requests:
     cpu: "1000m"
     memory: "4Gi"

    The file should looks as follows:

    ...
apiVersion: weblogic.oracle/v1
kind: Cluster
metadata:
  name: governancedomain-oim-cluster
  namespace: oigns
spec:
  clusterName: oim_cluster
  serverService:
    precreateService: true
  replicas: 0
  serverPod:
    env:
    - name: USER_MEM_ARGS
      value: "-XX:+UseContainerSupport -Djava.security.egd=file:/dev/./urandom -Xms8192m -Xmx8192m"
    resources:
      limits:
        cpu: "2"
        memory: "8Gi"
      requests:
        cpu: "1000m"
        memory: "4Gi"
...

    Note: The above CPU and memory values are for examples only. For Enterprise Deployments, please review the performance recommendations and sizing requirements in Enterprise Deployment Guide for Oracle Identity and Access Management in a Kubernetes Cluster.

    Note: Limits and requests for CPU resources are measured in CPU units. One CPU in Kubernetes is equivalent to 1 vCPU/Core for cloud providers, and 1 hyperthread on bare-metal Intel processors. An “m” suffix in a CPU attribute indicates ‘milli-CPU’, so 500m is 50% of a CPU. Memory can be expressed in various units, where one Mi is one IEC unit mega-byte (1024^2), and one Gi is one IEC unit giga-byte (1024^3). For more information, see Resource Management for Pods and Containers, Assign Memory Resources to Containers and Pods, and Assign CPU Resources to Containers and Pods.

    Note: The parameters above are also utilized by the Kubernetes Horizontal Pod Autoscaler (HPA). For more details on HPA, see Kubernetes Horizontal Pod Autoscaler.

    Note: If required you can also set the same resources and limits for the governancedomain-soa-cluster.

Run the create domain scripts

  1. Create the Kubernetes resource using the following command:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv/output/weblogic-domains/<domain_uid>
$ kubectl apply -f domain.yaml

    For example:

    $ cd $WORKDIR/kubernetes/create-oim-domain/domain-home-on-pv/output/weblogic-domains/governancedomain
$ kubectl apply -f domain.yaml

    The output will look similar to the following:

    domain.weblogic.oracle/governancedomain unchanged
cluster.weblogic.oracle/governancedomain-oim-cluster created
cluster.weblogic.oracle/governancedomain-soa-cluster created

  2. Run the following command to view the status of the OIG pods:

    $ kubectl get pods -n oigns

    The output will initially look similar to the following:

    NAME                                                        READY   STATUS      RESTARTS   AGE
governancedomain-create-fmw-infra-sample-domain-job-8cww8   0/1     Completed   0          27m
governancedomain-introspect-domain-job-p4brt                1/1     Running     0          6s
helper                                                      1/1     Running     0          3h30m

    The introspect-domain-job pod will be displayed first. Run the command again after several minutes and check to see that the Administration Server and SOA Server are both started. When started they should have STATUS = Running and READY = 1/1.

    NAME                                                        READY   STATUS      RESTARTS   AGE/
governancedomain-adminserver                                1/1     Running     0          7m30s
governancedomain-create-fmw-infra-sample-domain-job-8cww8   0/1     Completed   0          35m
governancedomain-soa-server1                                1/1     Running     0          4m
helper                                                      1/1     Running     0          3h38m

    Note: It will take several minutes before all the pods listed above show. When a pod has a STATUS of 0/1 the pod is started but the OIG 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 governancedomain-adminserver -n oigns
$ kubectl logs governancedomain-soa-server1 -n oigns

  3. Check the clusters using the following command:

    $ kubectl get cluster -n oigns

    The output will look similar to the following:

    NAME                           AGE
governancedomain-oim-cluster   9m
governancedomain-soa-cluster   9m

  4. Start the OIM server using the following command:

    $ kubectl patch cluster -n <namespace> <OIMClusterName> --type=merge -p '{"spec":{"replicas":<initialManagedServerReplicas>}}'

    For example:

    $ kubectl patch cluster -n oigns governancedomain-oim-cluster --type=merge -p '{"spec":{"replicas":1}}'

    The output will look similar to the following:

    cluster.weblogic.oracle/governancedomain-oim-cluster patched

  5. Run the following command to view the status of the OIG pods:

    $ kubectl get pods -n oigns

    The output will initially look similar to the following:

    NAME                                                        READY   STATUS      RESTARTS   AGE
governancedomain-adminserver                                1/1     Running     0          7m30s
governancedomain-create-fmw-infra-sample-domain-job-8cww8   0/1     Completed   0          35m
governancedomain-oim-server1                                1/1     Running     0          4m25s
governancedomain-soa-server1                                1/1     Running     0          4m
helper                                                      1/1     Running     0          3h38m

    Note: It will take several minutes before the governancedomain-oim-server1 pod has a STATUS of 1/1. While the pod is starting you can check the startup status in the pod log, by running the following command:

    $ kubectl logs governancedomain-oim-server1 -n oigns

Verify the results

Verify the domain, pods and services

  1. 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 oigns

    The output will look similar to the following:

    NAME                                                            READY   STATUS      RESTARTS   AGE
pod/governancedomain-adminserver                                1/1     Running     0          19m30s
pod/governancedomain-create-fmw-infra-sample-domain-job-8cww8   0/1     Completed   0          47m
pod/governancedomain-oim-server1                                1/1     Running     0          16m25s
pod/governancedomain-soa-server1                                1/1     Running     0          16m
pod/helper                                                      1/1     Running     0          3h50m

NAME                                           TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)               AGE
service/governancedomain-adminserver           ClusterIP   None             <none>        7001/TCP              28m
service/governancedomain-cluster-oim-cluster   ClusterIP   10.106.198.40    <none>        14002/TCP,14000/TCP   25m
service/governancedomain-cluster-soa-cluster   ClusterIP   10.102.218.11    <none>        8001/TCP              25m
service/governancedomain-oim-server1           ClusterIP   None             <none>        14002/TCP,14000/TCP   16m24s
service/governancedomain-oim-server2           ClusterIP   10.97.32.112     <none>        14002/TCP,14000/TCP   25m
service/governancedomain-oim-server3           ClusterIP   10.100.233.109   <none>        14002/TCP,14000/TCP   25m
service/governancedomain-oim-server4           ClusterIP   10.96.154.17     <none>        14002/TCP,14000/TCP   25m
service/governancedomain-oim-server5           ClusterIP   10.103.222.213   <none>        14002/TCP,14000/TCP   25m
service/governancedomain-soa-server1           ClusterIP   None             <none>        8001/TCP              25m
service/governancedomain-soa-server2           ClusterIP   10.104.43.118    <none>        8001/TCP              25m
service/governancedomain-soa-server3           ClusterIP   10.110.180.120   <none>        8001/TCP              25m
service/governancedomain-soa-server4           ClusterIP   10.99.161.73     <none>        8001/TCP              25m
service/governancedomain-soa-server5           ClusterIP   10.97.67.196     <none>        8001/TCP              25m

NAME                                                            COMPLETIONS   DURATION   AGE
job.batch/governancedomain-create-fmw-infra-sample-domain-job   1/1           3m6s       125m

NAME                                      AGE
domain.weblogic.oracle/governancedomain   24m

NAME                                                   AGE
cluster.weblogic.oracle/governancedomain-oim-cluster   23m
cluster.weblogic.oracle/governancedomain-soa-cluster   23m

The default domain created by the script has the following characteristics:

  • An Administration Server named AdminServer listening on port 7001.
  • A configured OIG cluster named oig_cluster of size 5.
  • A configured SOA cluster named soa_cluster of size 5.
  • One started OIG managed Server, named oim_server1, listening on port 14000.
  • One started SOA managed Server, named soa_server1, listening on port 8001.
  • Log files that are located in <persistent_volume>/logs/<domainUID>

Verify the domain

  1. Run the following command to describe the domain:

    $ kubectl describe domain <domain_uid> -n <namespace>

    For example:

    $ kubectl describe domain governancedomain -n oigns

    The output will look similar to the following:

    Name:         governancedomain
Namespace:    oigns
Labels:       weblogic.domainUID=governancedomain
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:  1247307
  UID:               4933be73-df97-493f-a20c-bf1e24f6b3f2
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
   Server Start Policy:  IfNeeded
  Clusters:
    Name:                          governancedomain-oim-cluster
    Name:                          governancedomain-soa-cluster
  Data Home:
  Domain Home:                     /u01/oracle/user_projects/domains/governancedomain
  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/oig_cpu:12.2.1.4-jdk8-ol8-<April'24>
  Image Pull Policy:               IfNotPresent
  Image Pull Secrets:
    Name:                           orclcred
  Include Server Out In Pod Log:    true
  Log Home:                         /u01/oracle/user_projects/domains/logs/governancedomain
  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:     governancedomain-domain-pvc
  Server Start Policy:  IfNeeded
  Web Logic Credentials Secret:
    Name:  oig-domain-credentials
Status:
  Clusters:
    Cluster Name:  oim_cluster
    Conditions:
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Available
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Completed
    Label Selector:          weblogic.domainUID=governancedomain,weblogic.clusterName=oim_cluster
    Maximum Replicas:        5
    Minimum Replicas:        0
    Observed Generation:     2
    Ready Replicas:          1
    Replicas:                1
    Replicas Goal:           1
    Cluster Name:            soa_cluster
    Conditions:
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Available
      Last Transition Time:  <DATE>
      Status:                True
      Type:                  Completed
    Label Selector:          weblogic.domainUID=governancedomain,weblogic.clusterName=soa_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:  oim_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:   oim_server1
    State:         RUNNING
    State Goal:    RUNNING
    Cluster Name:  oim_cluster
    Server Name:   oim_server2
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oim_cluster
    Server Name:   oim_server3
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oim_cluster
    Server Name:   oim_server4
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  oim_cluster
    Server Name:   oim_server5
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  soa_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:   soa_server1
    State:         RUNNING
    State Goal:    RUNNING
    Cluster Name:  soa_cluster
    Server Name:   soa_server2
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  soa_cluster
    Server Name:   soa_server3
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  soa_cluster
    Server Name:   soa_server4
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
    Cluster Name:  soa_cluster
    Server Name:   soa_server5
    State:         SHUTDOWN
    State Goal:    SHUTDOWN
  Start Time:      <DATE>
Events:
  Type     Reason   Age                   From               Message
  ----     ------   ----                  ----               -------
  Normal   Created  35m                   weblogic.operator  Domain governancedomain was created.
  Normal   Changed  34m (x1127 over 35m)  weblogic.operator  Domain governancedomain was changed.
  Warning  Failed   34m (x227 over 35m)   weblogic.operator  Domain governancedomain failed due to 'Domain validation error': Cluster resource 'governancedomain-oim-cluster' not found in namespace 'oigns'
   Cluster resource 'governancedomain-soa-cluster' not found in namespace 'oigns'. Update the domain resource to correct the validation error.
  Warning  Unavailable  17m                weblogic.operator  Domain governancedomain is unavailable: an insufficient number of its servers that are expected to be running are ready.";
  Warning  Incomplete   17m                weblogic.operator  Domain governancedomain is incomplete for one or more of the following reasons: there are failures detected, there are pending server shutdowns, or not all servers expected to be running are ready and at their target image, auxiliary images, restart version, and introspect version.
  Normal   Completed    13m (x2 over 26m)  weblogic.operator  Domain governancedomain 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.
  Normal   Available    13m (x2 over 26m)  weblogic.operator  Domain governancedomain is available: a sufficient number of its servers have reached the ready state.

    In the Status section of the output, the available servers and clusters are listed.

Verify the pods

  1. Run the following command to see the pods running the servers and which nodes they are running on:

    $ kubectl get pods -n <namespace> -o wide

    For example:

    $ kubectl get pods -n oigns -o wide

    The output will look similar to the following:

    NAME                                                        READY   STATUS      RESTARTS   AGE     IP              NODE           NOMINATED NODE   READINESS GATES
governancedomain-adminserver                                1/1     Running     0          24m     10.244.1.42   worker-node2   <none>           <none>
governancedomain-create-fmw-infra-sample-domain-job-8cww8   0/1     Completed   0          52m     10.244.1.40   worker-node2   <none>           <none>
governancedomain-oim-server1                                1/1     Running     0          52m     10.244.1.44   worker-node2   <none>           <none>
governancedomain-soa-server1                                1/1     Running     0          21m     10.244.1.43   worker-node2   <none>           <none>
helper                                                      1/1     Running     0          3h55m   10.244.1.39   worker-node2   <none>           <none>

    You are now ready to configure an Ingress to direct traffic for your OIG domain as per Configure an ingress for an OIG domain.