7.2.7 WDT OIGデプロイメントの確認
ドメイン、ポッドおよびサービスの確認
次のコマンドを実行して、ドメイン、サーバー・ポッドおよびサービスが作成され、ステータスが
1/1
のREADY
状態であることを確認します:kubectl get all,domains -n <domain_namespace>
例:kubectl get all,domains -n oigns
出力は次のようになります: NAME READY STATUS RESTARTS AGE
pod/governancedomain-adminserver 1/1 Running 0 25m
pod/governancedomain-oim-server1 1/1 Running 0 7m18s
pod/governancedomain-soa-server1 1/1 Running 0 20m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/governancedomain-adminserver ClusterIP None <none> 7001/TCP 25m
service/governancedomain-cluster-oim-cluster ClusterIP 10.102.36.107 <none> 14002/TCP,14000/TCP 20m
service/governancedomain-cluster-soa-cluster ClusterIP 10.102.230.187 <none> 7003/TCP 20m
service/governancedomain-oim-server1 ClusterIP None <none> 14002/TCP,14000/TCP 7m18s
service/governancedomain-oim-server2 ClusterIP 10.111.183.16 <none> 14002/TCP,14000/TCP 20m
service/governancedomain-oim-server3 ClusterIP 10.107.144.169 <none> 14002/TCP,14000/TCP 20m
service/governancedomain-oim-server4 ClusterIP 10.110.18.114 <none> 14002/TCP,14000/TCP 20m
service/governancedomain-oim-server5 ClusterIP 10.106.220.13 <none> 14002/TCP,14000/TCP 20m
service/governancedomain-soa-server1 ClusterIP None <none> 7003/TCP 20m
service/governancedomain-soa-server2 ClusterIP 10.104.204.68 <none> 7003/TCP 20m
service/governancedomain-soa-server3 ClusterIP 10.110.104.108 <none> 7003/TCP 20m
service/governancedomain-soa-server4 ClusterIP 10.103.117.118 <none> 7003/TCP 20m
service/governancedomain-soa-server5 ClusterIP 10.101.65.38 <none> 7003/TCP 20m
NAME AGE
domain.weblogic.oracle/governancedomain 32m
NAME AGE
cluster.weblogic.oracle/governancedomain-oim-cluster 32m
cluster.weblogic.oracle/governancedomain-soa-cluster 32m
スクリプトによって作成されたデフォルト・ドメインには、次の特性があります:
- ポート
7001
でリスニングするAdminServer
という管理サーバー。 - サイズが
5
のoig_cluster
という構成済OIGクラスタ。 - サイズが
5
のsoa_cluster
という構成済SOAクラスタ。 - ポート
14100
でリスニングするoim_server1
という1つの起動されたOIG管理対象サーバー。 - ポート
7003
でリスニングするsoa_server1
という1つの起動されたSOA管理対象サーバー。 <persistent_volume>/logs/<domainUID>
に配置されたログ・ファイル。
OIGデプロイメントに失敗した場合は、「一般的なトラブルシューティング」を参照してください。
ドメインの確認
次のコマンドを実行して、ドメインを説明します:
kubectl describe domain <domain_uid> -n <domain_namespace>
例:kubectl describe domain governancedomain -n oigns
出力は次のようになります: Name: governancedomain
Namespace: oigns
Labels: weblogic.domainUID=governancedomain
Annotations: <none>
API Version: weblogic.oracle/v9
Kind: Domain
Metadata:
Creation Timestamp: <DATE>
Generation: 1
Resource Version: 1013312
UID: b5b4446b-b056-431f-8ae4-db470ac7731e
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
Configuration:
Initialize Domain On PV:
Domain:
Create If Not Exists: DomainAndRCU
Domain Creation Images:
Image: container-registry.example.com/mytenancy/idm:oig-aux-generic-v1
Domain Type: OIG
Persistent Volume:
Metadata:
Name: governancedomain-domain-pv
Spec:
Capacity:
Storage: 10Gi
Nfs:
Path: /nfs_volumes/oig/governancedomainpv
Server: mynfsserver
Persistent Volume Reclaim Policy: Retain
Storage Class Name: governancedomain-domain-storage-class
Persistent Volume Claim:
Metadata:
Name: governancedomain-domain-pvc
Spec:
Resources:
Requests:
Storage: 10Gi
Storage Class Name: governancedomain-domain-storage-class
Volume Name: governancedomain-domain-pv
Override Distribution Strategy: Dynamic
Secrets:
governancedomain-rcu-credentials
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:14.1.2.1.0-jdk8-ol8-<YYMMDD>
Image Pull Policy: IfNotPresent
Image Pull Secrets:
Name: orclcred
Name: privatecred
Include Server Out In Pod Log: true
Log Home: /u01/oracle/user_projects/domains/logs/governancedomain
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: FRONTENDHOST
Value: example.com
Name: FRONTENDPORT
Value: 14000
Name: WLSDEPLOY_PROPERTIES
Value: -Dwdt.config.disable.rcu.drop.schema=true
Env From:
Secret Ref:
Name: governancedomain-rcu-credentials
Init Containers:
Command:
/bin/bash
-c
mkdir -p /u01/oracle/user_projects/domains/ConnectorDefaultDirectory
mkdir -p /u01/oracle/user_projects/domains/wdt-logs
Image: container-registry.oracle.com/middleware/oig_cpu:14.1.2.1.0-jdk8-ol8-<YYMMDD>
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: governancedomain-domain-pvc
Server Start Policy: IfNeeded
Web Logic Credentials Secret:
Name: governancedomain-weblogic-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: doc-worker2
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: doc-worker1
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: doc-worker1
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: <none>
出力のStatus
セクションに、使用可能なサーバーおよびクラスタがリストされます。
ポッドの確認
次のコマンドを実行して、ポッドおよびポッドが実行されているノードを表示します:
kubectl get pods -n <domain_namespace> -o wide
例:kubectl get pods -n oigns -o wide
出力は次のようになります:NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
governancedomain-adminserver 1/1 Running 0 26m 10.244.1.42 worker-node2 <none> <none
governancedomain-oim-server1 1/1 Running 0 7m56s 10.244.1.44 worker-node2 <none> <none>
governancedomain-soa-server1 1/1 Running 0 21m 10.244.1.43 worker-node2 <none> <none>
イングレスの構成
ドメインが正常にデプロイされ、前述のチェックをすべて確認したら、イングレスを構成する準備が完了します。「イングレスの構成」を参照してください。