7.2.7 WDT OAMデプロイメントの確認
ドメイン、ポッドおよびサービスの確認
次のコマンドを実行して、ドメイン、サーバー・ポッドおよびサービスが作成され、ステータスが
1/1のREADY状態であることを確認します:kubectl get all,domains -n <domain_namespace>kubectl get all,domains -n oamnsNAME READY STATUS RESTARTS AGE
pod/accessdomain-adminserver 1/1 Running 0 12m
pod/accessdomain-oam-policy-mgr1 1/1 Running 0 4m19s
pod/accessdomain-oam-server1 1/1 Running 0 4m19s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/accessdomain-adminserver ClusterIP None <none> 7001/TCP 12m
service/accessdomain-cluster-oam-cluster ClusterIP 10.104.17.83 <none> 14100/TCP 4m19s
service/accessdomain-cluster-policy-cluster ClusterIP 10.98.157.157 <none> 15100/TCP 4m19s
service/accessdomain-oam-policy-mgr1 ClusterIP None <none> 15100/TCP 4m19s
service/accessdomain-oam-policy-mgr2 ClusterIP 10.101.141.238 <none> 15100/TCP 4m19s
service/accessdomain-oam-policy-mgr3 ClusterIP 10.107.167.143 <none> 15100/TCP 4m19s
service/accessdomain-oam-policy-mgr4 ClusterIP 10.106.100.191 <none> 15100/TCP 4m19s
service/accessdomain-oam-policy-mgr5 ClusterIP 10.105.5.126 <none> 15100/TCP 4m19s
service/accessdomain-oam-server1 ClusterIP None <none> 14100/TCP 4m19s
service/accessdomain-oam-server2 ClusterIP 10.98.248.74 <none> 14100/TCP 4m19s
service/accessdomain-oam-server3 ClusterIP 10.106.224.54 <none> 14100/TCP 4m19s
service/accessdomain-oam-server4 ClusterIP 10.104.241.109 <none> 14100/TCP 4m19s
service/accessdomain-oam-server5 ClusterIP 10.96.189.205 <none> 14100/TCP 4m19s
NAME AGE
domain.weblogic.oracle/accessdomain 18m
NAME AGE
cluster.weblogic.oracle/accessdomain-oam-cluster 18m
cluster.weblogic.oracle/accessdomain-policy-cluster 18m
スクリプトによって作成されたデフォルト・ドメインには、次の特性があります:
- ポート
7001でリスニングするAdminServerという管理サーバー。 - サイズが
5のoam_clusterという構成済OAMクラスタ。 - サイズが
5のpolicy_clusterという構成済ポリシー・マネージャ・クラスタ。 - ポート
14100でリスニングするoam_server1という1つの起動されたOAM管理対象サーバー。 - ポート
15100でリスニングするoam-policy-mgr1という1つの起動されたポリシー・マネージャ管理対象サーバー。 <persistent_volume>/logs/<domainUID>に配置されたログ・ファイル。
OAMデプロイメントに失敗した場合は、「既知の問題」の「WDTモデルを使用したドメイン作成の失敗」を参照してください。
ドメインの確認
次のコマンドを実行して、ドメインを説明します:
kubectl describe domain <domain_uid> -n <domain_namespace>
kubectl describe domain accessdomain -n oamnsName: accessdomain
Namespace: oamns
Labels: weblogic.domainUID=accessdomain
Annotations: <none>
API Version: weblogic.oracle/v9
Kind: Domain
Metadata:
Creation Timestamp: <DATE>
Generation: 1
Resource Version: 2930591
UID: 7eafcfd3-f0f3-436d-a1f0-87c31f042d62
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
Configuration:
Initialize Domain On PV:
Domain:
Create If Not Exists: DomainAndRCU
Domain Creation Images:
Image: container-registry.example.com/mytenancy/idm:oam-aux-generic-v1
Domain Type: OAM
Persistent Volume:
Metadata:
Name: accessdomain-domain-pv
Spec:
Capacity:
Storage: 10Gi
Nfs:
Path: /<NFS_PATH>/accessdomainpv
Server: <NFS_SERVER>
Persistent Volume Reclaim Policy: Retain
Storage Class Name: accessdomain-domain-storage-class
Persistent Volume Claim:
Metadata:
Name: accessdomain-domain-pvc
Spec:
Resources:
Requests:
Storage: 10Gi
Storage Class Name: accessdomain-domain-storage-class
Volume Name: accessdomain-domain-pv
Override Distribution Strategy: Dynamic
Secrets:
accessdomain-rcu-credentials
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:14.1.2.1.0-jdk17-ol8-<DDMMYY>
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
Max Cluster Concurrent Shutdown: 1
Max Cluster Concurrent Startup: 0
Max Cluster Unavailable: 1
Replace Variables In Java Options: false
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
Name: WLSDEPLOY_LOG_DIRECTORY
Value: /u01/oracle/user_projects/domains/wdt-logs
Name: WLSDEPLOY_PROPERTIES
Value: -Dwdt.config.disable.rcu.drop.schema=true
Init Containers:
Command:
/bin/bash
-c
mkdir -p /u01/oracle/user_projects/domains/wdt-logs
Image: container-registry.oracle.com/middleware/oam_cpu:14.1.2.1.0-jdk17-ol8-<DDMMYY>
Image Pull Policy: IfNotPresent
Name: compat-connector-init
Volume Mounts:
Mount Path: /u01/oracle/user_projects
Name: weblogic-domain-storage-volume
Volume Mounts:
Mount Path: /u01/oracle/user_projects
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-weblogic-credentials
Status:
Clusters:
Cluster Name: oam_cluster
Conditions:
Last Transition Time: <DATE>
Status: False
Type: Available
Last Transition Time: <DATE>
Status: False
Type: Completed
Label Selector: weblogic.domainUID=accessdomain,weblogic.clusterName=oam_cluster
Maximum Replicas: 5
Minimum Replicas: 0
Observed Generation: 1
Replicas: 1
Replicas Goal: 1
Cluster Name: policy_cluster
Conditions:
Last Transition Time: <DATE>
Status: False
Type: Available
Last Transition Time: <DATE>
Status: False
Type: Completed
Label Selector: weblogic.domainUID=accessdomain,weblogic.clusterName=policy_cluster
Maximum Replicas: 5
Minimum Replicas: 0
Observed Generation: 1
Replicas: 1
Replicas Goal: 1
Conditions:
Last Transition Time: <DATE>
Message: No application servers are ready.
Status: False
Type: Available
Last Transition Time: <DATE>
Status: False
Type: Completed
Observed Generation: 1
Servers:
Health:
Activation Time: <DATE>
Overall Health: ok
Subsystems:
Subsystem Name: ServerRuntime
Symptoms:
Node Name: worker-node1
Pod Phase: Running
Pod Ready: True
Server Name: AdminServer
State: RUNNING
State Goal: RUNNING
Cluster Name: oam_cluster
Node Name: worker-node2
Pod Phase: Running
Pod Ready: False
Server Name: oam_server1
State: STARTING
State Goal: SHUTDOWN
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
Node Name: worker-node1
Pod Phase: Running
Pod Ready: False
Server Name: oam_policy_mgr1
State: STARTING
State Goal: SHUTDOWN
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 19m weblogic.operator Domain accessdomain was created.
Warning Failed 19m weblogic.operator Domain accessdomain failed due to 'Persistent volume claim unbound': PersistentVolumeClaim 'accessdomain-domain-pvc' is not bound; the status phase is 'Pending'.. Operator is waiting for the persistent volume claim to be bound, it may be a temporary condition. If this condition persists, then ensure that the PVC has a correct volume name or storage class name and is in bound status..
Normal PersistentVolumeClaimBound 19m weblogic.operator The persistent volume claim is bound and ready.
Normal Available 3m19s weblogic.operator Domain accessdomain is available: a sufficient number of its servers have reached the ready state.
Normal Completed 3m19s 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.
Statusセクションに、使用可能なサーバーおよびクラスタがリストされます。
ポッドの確認
次のコマンドを実行して、ポッドおよびポッドが実行されているノードを表示します:
kubectl get pods -n <domain_namespace> -o wide
kubectl get pods -n oamns -o wideNAME 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-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>
イングレスの構成
ドメインが正常にデプロイされ、前述のチェックをすべて確認したら、イングレスを構成する準備が完了します。「イングレスの構成」を参照してください。