|
6 | 6 | # extractDomainResource script to generate a domain.yaml |
7 | 7 | # |
8 | 8 | kubernetes: |
9 | | - apiVersion: "weblogic.oracle/v8" |
10 | | - kind: Domain |
11 | | - metadata: |
12 | | - name: %DOMAIN_UID% |
13 | | - namespace: "%NAMESPACE%" |
14 | | - labels: |
15 | | - #weblogic.resourceVersion: "domain-v2" |
16 | | - weblogic.domainUID: %DOMAIN_UID% |
17 | | - spec: |
18 | | - # The WebLogic Domain Home |
19 | | - domainHome: %DOMAIN_HOME% |
| 9 | + domain: |
| 10 | + metadata: |
| 11 | + name: %DOMAIN_UID% |
| 12 | + namespace: "%NAMESPACE%" |
| 13 | + spec: |
| 14 | + # The WebLogic Domain Home |
| 15 | + domainHome: %DOMAIN_HOME% |
20 | 16 |
|
21 | | - # The domain home source type |
22 | | - # Set to PersistentVolume for domain-in-pv, Image for domain-in-image, or FromModel for model-in-image |
23 | | - domainHomeSourceType: %DOMAIN_HOME_SOURCE_TYPE% |
| 17 | + # The domain home source type |
| 18 | + # Set to PersistentVolume for domain-in-pv, Image for domain-in-image, or FromModel for model-in-image |
| 19 | + domainHomeSourceType: %DOMAIN_HOME_SOURCE_TYPE% |
24 | 20 |
|
25 | | - # The WebLogic Server Docker image that the Operator uses to start the domain |
26 | | - image: "%WEBLOGIC_IMAGE%" |
| 21 | + # The WebLogic Server Docker image that the Operator uses to start the domain |
| 22 | + image: "%WEBLOGIC_IMAGE%" |
27 | 23 |
|
28 | | - # imagePullPolicy defaults to "Always" if image version is :latest |
29 | | - imagePullPolicy: %WEBLOGIC_IMAGE_PULL_POLICY% |
| 24 | + # imagePullPolicy defaults to "Always" if image version is :latest |
| 25 | + imagePullPolicy: %WEBLOGIC_IMAGE_PULL_POLICY% |
30 | 26 |
|
31 | | - # Identify which Secret contains the credentials for pulling an image |
32 | | - %WEBLOGIC_IMAGE_PULL_SECRET_PREFIX%imagePullSecrets: |
33 | | - %WEBLOGIC_IMAGE_PULL_SECRET_PREFIX% - name: "%WEBLOGIC_IMAGE_PULL_SECRET_NAME%" |
34 | | - # Identify which Secret contains the WebLogic Admin credentials (note that there is an example of |
35 | | - # how to create that Secret at the end of this file) |
36 | | - webLogicCredentialsSecret: |
37 | | - name: '%WEBLOGIC_CREDENTIALS_SECRET_NAME%' |
| 27 | + # Identify which Secret contains the credentials for pulling an image |
| 28 | + %WEBLOGIC_IMAGE_PULL_SECRET_PREFIX%imagePullSecrets: |
| 29 | + %WEBLOGIC_IMAGE_PULL_SECRET_PREFIX% - name: "%WEBLOGIC_IMAGE_PULL_SECRET_NAME%" |
| 30 | + # Identify which Secret contains the WebLogic Admin credentials (note that there is an example of |
| 31 | + # how to create that Secret at the end of this file) |
| 32 | + webLogicCredentialsSecret: |
| 33 | + name: '%WEBLOGIC_CREDENTIALS_SECRET_NAME%' |
38 | 34 |
|
39 | | - # Whether to include the server out file into the pod's stdout, default is true |
40 | | - includeServerOutInPodLog: %INCLUDE_SERVER_OUT_IN_POD_LOG% |
| 35 | + # Whether to include the server out file into the pod's stdout, default is true |
| 36 | + includeServerOutInPodLog: %INCLUDE_SERVER_OUT_IN_POD_LOG% |
41 | 37 |
|
42 | | - # Whether to enable log home |
43 | | - %LOG_HOME_ON_PV_PREFIX%logHomeEnabled: %LOG_HOME_ENABLED% |
| 38 | + # Whether to enable log home |
| 39 | + %LOG_HOME_ON_PV_PREFIX%logHomeEnabled: %LOG_HOME_ENABLED% |
44 | 40 |
|
45 | | - # Whether to write HTTP access log file to log home |
46 | | - #%LOG_HOME_ON_PV_PREFIX%httpAccessLogInLogHome: %HTTP_ACCESS_LOG_IN_LOG_HOME% |
| 41 | + # Whether to write HTTP access log file to log home |
| 42 | + #%LOG_HOME_ON_PV_PREFIX%httpAccessLogInLogHome: %HTTP_ACCESS_LOG_IN_LOG_HOME% |
47 | 43 |
|
48 | | - # The in-pod location for domain log, server logs, server out, and Node Manager log files |
49 | | - %LOG_HOME_ON_PV_PREFIX%logHome: %LOG_HOME% |
50 | | - # An (optional) in-pod location for data storage of default and custom file stores. |
51 | | - # If not specified or the value is either not set or empty (e.g. dataHome: "") then the |
52 | | - # data storage directories are determined from the WebLogic domain home configuration. |
53 | | - dataHome: "%DATA_HOME%" |
| 44 | + # The in-pod location for domain log, server logs, server out, and Node Manager log files |
| 45 | + %LOG_HOME_ON_PV_PREFIX%logHome: %LOG_HOME% |
| 46 | + # An (optional) in-pod location for data storage of default and custom file stores. |
| 47 | + # If not specified or the value is either not set or empty (e.g. dataHome: "") then the |
| 48 | + # data storage directories are determined from the WebLogic domain home configuration. |
| 49 | + dataHome: "%DATA_HOME%" |
54 | 50 |
|
55 | | - replicas: %INITIAL_MANAGED_SERVER_REPLICAS% |
| 51 | + replicas: %INITIAL_MANAGED_SERVER_REPLICAS% |
56 | 52 |
|
57 | | - # serverStartPolicy legal values are "NEVER", "IF_NEEDED", or "ADMIN_ONLY" |
58 | | - # This determines which WebLogic Servers the Operator will start up when it discovers this Domain |
59 | | - # - "NEVER" will not start any server in the domain |
60 | | - # - "ADMIN_ONLY" will start up only the administration server (no managed servers will be started) |
61 | | - # - "IF_NEEDED" will start all non-clustered servers, including the administration server and clustered servers up to the replica count |
62 | | - serverStartPolicy: %SERVER_START_POLICY% |
| 53 | + # serverStartPolicy legal values are "Never, "IfNeeded", or "AdminOnly" |
| 54 | + # This determines which WebLogic Servers the Operator will start up when it discovers this Domain |
| 55 | + # - "Never" will not start any server in the domain |
| 56 | + # - "AdminOnly" will start up only the administration server (no managed servers will be started) |
| 57 | + # - "IfNeeded" will start all non-clustered servers, including the administration server and clustered servers up to the replica count |
| 58 | + serverStartPolicy: %SERVER_START_POLICY% |
63 | 59 |
|
64 | | - serverPod: |
65 | | - # an (optional) list of environment variable to be set on the servers |
66 | | - env: |
67 | | - - name: JAVA_OPTIONS |
68 | | - value: "%JAVA_OPTIONS%" |
69 | | - - name: USER_MEM_ARGS |
70 | | - value: "-Djava.security.egd=file:/dev/./urandom " |
71 | | - %OPTIONAL_SERVERPOD_RESOURCES% |
72 | | - %LOG_HOME_ON_PV_PREFIX%volumes: |
73 | | - %LOG_HOME_ON_PV_PREFIX% - name: 'weblogic-domain-storage-volume' |
74 | | - %LOG_HOME_ON_PV_PREFIX% persistentVolumeClaim: |
75 | | - %LOG_HOME_ON_PV_PREFIX% claimName: '%DOMAIN_PVC_NAME%' |
76 | | - %LOG_HOME_ON_PV_PREFIX%volumeMounts: |
77 | | - %LOG_HOME_ON_PV_PREFIX% - name: 'weblogic-domain-storage-volume' |
78 | | - %LOG_HOME_ON_PV_PREFIX% mountPath: %DOMAIN_ROOT_DIR% |
79 | | - |
80 | | - # adminServer is used to configure the desired behavior for starting the administration server. |
81 | | - adminServer: |
82 | | - %EXPOSE_ANY_CHANNEL_PREFIX%adminService: |
83 | | - %EXPOSE_ANY_CHANNEL_PREFIX% channels: |
84 | | - # The Admin Server's NodePort |
85 | | - %EXPOSE_ANY_CHANNEL_PREFIX% - channelName: default |
86 | | - %EXPOSE_ADMIN_PORT_PREFIX% nodePort: %ADMIN_NODE_PORT% |
87 | | - # Uncomment to export the T3Channel as a service |
88 | | - %EXPOSE_T3_CHANNEL_PREFIX% - channelName: T3Channel |
| 60 | + serverPod: |
| 61 | + # an (optional) list of environment variable to be set on the servers |
| 62 | + env: |
| 63 | + - name: JAVA_OPTIONS |
| 64 | + value: "%JAVA_OPTIONS%" |
| 65 | + - name: USER_MEM_ARGS |
| 66 | + value: "-Djava.security.egd=file:/dev/./urandom " |
| 67 | + %OPTIONAL_SERVERPOD_RESOURCES% |
| 68 | + %LOG_HOME_ON_PV_PREFIX%volumes: |
| 69 | + %LOG_HOME_ON_PV_PREFIX% - name: 'weblogic-domain-storage-volume' |
| 70 | + %LOG_HOME_ON_PV_PREFIX% persistentVolumeClaim: |
| 71 | + %LOG_HOME_ON_PV_PREFIX% claimName: '%DOMAIN_PVC_NAME%' |
| 72 | + %LOG_HOME_ON_PV_PREFIX%volumeMounts: |
| 73 | + %LOG_HOME_ON_PV_PREFIX% - name: 'weblogic-domain-storage-volume' |
| 74 | + %LOG_HOME_ON_PV_PREFIX% mountPath: %DOMAIN_ROOT_DIR% |
89 | 75 |
|
| 76 | + # adminServer is used to configure the desired behavior for starting the administration server. |
| 77 | + adminServer: |
| 78 | + %EXPOSE_ANY_CHANNEL_PREFIX%adminService: |
| 79 | + %EXPOSE_ANY_CHANNEL_PREFIX% channels: |
| 80 | + # The Admin Server's NodePort |
| 81 | + %EXPOSE_ANY_CHANNEL_PREFIX% - channelName: default |
| 82 | + %EXPOSE_ADMIN_PORT_PREFIX% nodePort: %ADMIN_NODE_PORT% |
| 83 | + # Uncomment to export the T3Channel as a service |
| 84 | + %EXPOSE_T3_CHANNEL_PREFIX% - channelName: T3Channel |
| 85 | + |
| 86 | + # References to Cluster resources that describe the lifecycle options for all |
| 87 | + # the Managed Server members of a WebLogic cluster, including Java |
| 88 | + # options, environment variables, additional Pod content, and the ability to |
| 89 | + # explicitly start, stop, or restart cluster members. The Cluster resource |
| 90 | + # must describe a cluster that already exists in the WebLogic domain |
| 91 | + # configuration. |
| 92 | + clusters: |
| 93 | + - name: %DOMAIN_UID%-%CLUSTER_NAME% |
| 94 | + |
| 95 | + # clusters is used to configure the desired behavior for starting member servers of a cluster. |
| 96 | + # If you use this entry, then the rules will be applied to ALL servers that are members of the named clusters. |
| 97 | + clusters: |
| 98 | + - metadata: |
| 99 | + name: %DOMAIN_UID%-%CLUSTER_NAME% |
| 100 | + namespace: "%NAMESPACE%" |
| 101 | + spec: |
| 102 | + clusterName: %CLUSTER_NAME% |
| 103 | + replicas: %INITIAL_MANAGED_SERVER_REPLICAS% |
0 commit comments