You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/domains/Cluster.json
+4-66Lines changed: 4 additions & 66 deletions
Original file line number
Diff line number
Diff line change
@@ -165,68 +165,6 @@
165
165
"Map": {
166
166
"type": "object"
167
167
},
168
-
"ProbeTuning": {
169
-
"type": "object",
170
-
"properties": {
171
-
"failureThreshold": {
172
-
"default": 1,
173
-
"description": "Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1.",
174
-
"type": "integer",
175
-
"minimum": 1
176
-
},
177
-
"periodSeconds": {
178
-
"description": "The number of seconds between checks.",
179
-
"type": "integer"
180
-
},
181
-
"timeoutSeconds": {
182
-
"description": "The number of seconds with no response that indicates a failure.",
183
-
"type": "integer"
184
-
},
185
-
"successThreshold": {
186
-
"default": 1,
187
-
"description": "Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe.",
188
-
"type": "integer",
189
-
"minimum": 1
190
-
},
191
-
"initialDelaySeconds": {
192
-
"description": "The number of seconds before the first check is performed.",
193
-
"type": "integer"
194
-
}
195
-
}
196
-
},
197
-
"ReadinessProbe": {
198
-
"type": "object",
199
-
"properties": {
200
-
"failureThreshold": {
201
-
"default": 1,
202
-
"description": "Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1.",
203
-
"type": "integer",
204
-
"minimum": 1
205
-
},
206
-
"httpGetActionPath": {
207
-
"description": "Path to access for the readiness probe. Defaults to /weblogic/ready",
208
-
"type": "string"
209
-
},
210
-
"periodSeconds": {
211
-
"description": "The number of seconds between checks.",
212
-
"type": "integer"
213
-
},
214
-
"timeoutSeconds": {
215
-
"description": "The number of seconds with no response that indicates a failure.",
216
-
"type": "integer"
217
-
},
218
-
"successThreshold": {
219
-
"default": 1,
220
-
"description": "Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe.",
221
-
"type": "integer",
222
-
"minimum": 1
223
-
},
224
-
"initialDelaySeconds": {
225
-
"description": "The number of seconds before the first check is performed.",
226
-
"type": "integer"
227
-
}
228
-
}
229
-
},
230
168
"ServerPod": {
231
169
"type": "object",
232
170
"properties": {
@@ -293,8 +231,8 @@
293
231
}
294
232
},
295
233
"readinessProbe": {
296
-
"description": "Settings for the readiness probe associated with a WebLogic Server instance.",
297
-
"$ref": "#/definitions/ReadinessProbe"
234
+
"description": "Settings for the readiness probe associated with a WebLogic Server instance. If not specified, the operator will create an HTTP probe accessing the /weblogic/ready path. If an HTTP probe is specified then the operator will fill in `path`, `port`, and `scheme`, if they are missing. The operator will also fill in any missing tuning-related fields if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different HTTP path to access.",
"description": "Container-level security attributes. Will override any matching Pod-level attributes. See `kubectl explain pods.spec.containers.securityContext`. Beginning with operator version 4.0.5, if no value is specified for this field, the operator will use default content for container-level `securityContext`. More info: https://oracle.github.io/weblogic-kubernetes-operator/security/domain-security/pod-and-container/.",
@@ -316,8 +254,8 @@
316
254
"type": "integer"
317
255
},
318
256
"livenessProbe": {
319
-
"description": "Settings for the liveness probe associated with a WebLogic Server instance.",
320
-
"$ref": "#/definitions/ProbeTuning"
257
+
"description": "Settings for the liveness probe associated with a WebLogic Server instance. If not specified, the operator will create a probe that executes a script provided by the operator. The operator will also fill in any missing tuning-related fields, if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different script to execute.",
"description": "TopologySpreadConstraints describes how a group of pods ought to spread across topology domains. Scheduler will schedule pods in a way which abides by the constraints. All topologySpreadConstraints are ANDed.",
Copy file name to clipboardExpand all lines: documentation/domains/Cluster.md
+2-23Lines changed: 2 additions & 23 deletions
Original file line number
Diff line number
Diff line change
@@ -62,15 +62,15 @@ The specification of the operation of the WebLogic cluster. Required.
62
62
|`hostAliases`| Array of [Host Alias](k8s1.13.5.md#host-alias)| HostAliases is an optional list of hosts and IPs that will be injected into the pod's hosts file if specified. This is only valid for non-hostNetwork pods. |
63
63
|`initContainers`| Array of [Container](k8s1.13.5.md#container)| Initialization containers to be included in the server Pod. See `kubectl explain pods.spec.initContainers`. |
64
64
|`labels`| Map | The labels to be added to generated resources. The label names must not start with "weblogic.". |
65
-
|`livenessProbe`|[Probe Tuning](#probe-tuning)| Settings for the liveness probe associated with a WebLogic Server instance. |
65
+
|`livenessProbe`|[Probe](k8s1.13.5.md#probe)| Settings for the liveness probe associated with a WebLogic Server instance. If not specified, the operator will create a probe that executes a script provided by the operator. The operator will also fill in any missing tuning-related fields, if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different script to execute. |
66
66
|`maxPendingWaitTimeSeconds`| integer | The maximum time in seconds that the operator waits for a WebLogic Server pod to reach the running state before it considers the pod failed. Defaults to 5 minutes. |
67
67
|`maxReadyWaitTimeSeconds`| integer | The maximum time in seconds that the operator waits for a WebLogic Server pod to reach the ready state before it considers the pod failed. Defaults to 1800 seconds. |
68
68
|`nodeName`| string | NodeName is a request to schedule this Pod onto a specific Node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits the resource requirements. See `kubectl explain pods.spec.nodeName`. |
69
69
|`nodeSelector`| Map | Selector which must match a Node's labels for the Pod to be scheduled on that Node. See `kubectl explain pods.spec.nodeSelector`. |
70
70
|`podSecurityContext`|[Pod Security Context](k8s1.13.5.md#pod-security-context)| Pod-level security attributes. See `kubectl explain pods.spec.securityContext`. Beginning with operator version 4.0.5, if no value is specified for this field, the operator will use default content for the pod-level `securityContext`. More info: https://oracle.github.io/weblogic-kubernetes-operator/security/domain-security/pod-and-container/.|
71
71
|`priorityClassName`| string | If specified, indicates the Pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be the default or zero, if there is no default. See `kubectl explain pods.spec.priorityClassName`. |
72
72
|`readinessGates`| Array of [Pod Readiness Gate](k8s1.13.5.md#pod-readiness-gate)| If specified, all readiness gates will be evaluated for Pod readiness. A Pod is ready when all its containers are ready AND all conditions specified in the readiness gates have a status equal to "True". More info: https://github.com/kubernetes/community/blob/master/keps/sig-network/0007-pod-ready%2B%2B.md.|
73
-
|`readinessProbe`|[Readiness Probe](#readiness-probe)| Settings for the readiness probe associated with a WebLogic Server instance. |
73
+
|`readinessProbe`|[Probe](k8s1.13.5.md#probe)| Settings for the readiness probe associated with a WebLogic Server instance. If not specified, the operator will create an HTTP probe accessing the /weblogic/ready path. If an HTTP probe is specified then the operator will fill in `path`, `port`, and `scheme`, if they are missing. The operator will also fill in any missing tuning-related fields if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different HTTP path to access. |
74
74
|`resources`|[Resource Requirements](k8s1.13.5.md#resource-requirements)| Memory and CPU minimum requirements and limits for the WebLogic Server instance. See `kubectl explain pods.spec.containers.resources`. |
75
75
|`restartPolicy`| string | Restart policy for all containers within the Pod. One of Always, OnFailure, Never. Default to Always. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy. See `kubectl explain pods.spec.restartPolicy`. |
76
76
|`runtimeClassName`| string | RuntimeClassName refers to a RuntimeClass object in the node.k8s.io group, which should be used to run this Pod. If no RuntimeClass resource matches the named class, the Pod will not be run. If unset or empty, the "legacy" RuntimeClass will be used, which is an implicit class with an empty definition that uses the default runtime handler. More info: https://github.com/kubernetes/community/blob/master/keps/sig-node/0014-runtime-class.md This is an alpha feature and may change in the future. See `kubectl explain pods.spec.runtimeClassName`. |
@@ -99,27 +99,6 @@ The specification of the operation of the WebLogic cluster. Required.
99
99
|`status`| string | The status of the condition. Can be True, False. |
100
100
|`type`| string | The type of the condition. Valid types are Completed, Available, Failed, and Rolling. |
101
101
102
-
### Probe Tuning
103
-
104
-
| Name | Type | Description |
105
-
| --- | --- | --- |
106
-
|`failureThreshold`| integer | Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1. |
107
-
|`initialDelaySeconds`| integer | The number of seconds before the first check is performed. |
108
-
|`periodSeconds`| integer | The number of seconds between checks. |
109
-
|`successThreshold`| integer | Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe. |
110
-
|`timeoutSeconds`| integer | The number of seconds with no response that indicates a failure. |
111
-
112
-
### Readiness Probe
113
-
114
-
| Name | Type | Description |
115
-
| --- | --- | --- |
116
-
|`failureThreshold`| integer | Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1. |
117
-
|`httpGetActionPath`| string | Path to access for the readiness probe. Defaults to /weblogic/ready |
118
-
|`initialDelaySeconds`| integer | The number of seconds before the first check is performed. |
119
-
|`periodSeconds`| integer | The number of seconds between checks. |
120
-
|`successThreshold`| integer | Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe. |
121
-
|`timeoutSeconds`| integer | The number of seconds with no response that indicates a failure. |
Copy file name to clipboardExpand all lines: documentation/domains/Domain.json
+4-66Lines changed: 4 additions & 66 deletions
Original file line number
Diff line number
Diff line change
@@ -1006,68 +1006,6 @@
1006
1006
}
1007
1007
}
1008
1008
},
1009
-
"ProbeTuning": {
1010
-
"type": "object",
1011
-
"properties": {
1012
-
"failureThreshold": {
1013
-
"default": 1,
1014
-
"description": "Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1.",
1015
-
"type": "integer",
1016
-
"minimum": 1
1017
-
},
1018
-
"periodSeconds": {
1019
-
"description": "The number of seconds between checks.",
1020
-
"type": "integer"
1021
-
},
1022
-
"timeoutSeconds": {
1023
-
"description": "The number of seconds with no response that indicates a failure.",
1024
-
"type": "integer"
1025
-
},
1026
-
"successThreshold": {
1027
-
"default": 1,
1028
-
"description": "Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe.",
1029
-
"type": "integer",
1030
-
"minimum": 1
1031
-
},
1032
-
"initialDelaySeconds": {
1033
-
"description": "The number of seconds before the first check is performed.",
1034
-
"type": "integer"
1035
-
}
1036
-
}
1037
-
},
1038
-
"ReadinessProbe": {
1039
-
"type": "object",
1040
-
"properties": {
1041
-
"failureThreshold": {
1042
-
"default": 1,
1043
-
"description": "Number of times the check is performed before giving up. Giving up in case of liveness probe means restarting the container. In case of readiness probe, the Pod will be marked Unready. Defaults to 1.",
1044
-
"type": "integer",
1045
-
"minimum": 1
1046
-
},
1047
-
"httpGetActionPath": {
1048
-
"description": "Path to access for the readiness probe. Defaults to /weblogic/ready",
1049
-
"type": "string"
1050
-
},
1051
-
"periodSeconds": {
1052
-
"description": "The number of seconds between checks.",
1053
-
"type": "integer"
1054
-
},
1055
-
"timeoutSeconds": {
1056
-
"description": "The number of seconds with no response that indicates a failure.",
1057
-
"type": "integer"
1058
-
},
1059
-
"successThreshold": {
1060
-
"default": 1,
1061
-
"description": "Minimum number of times the check needs to pass for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness Probe.",
1062
-
"type": "integer",
1063
-
"minimum": 1
1064
-
},
1065
-
"initialDelaySeconds": {
1066
-
"description": "The number of seconds before the first check is performed.",
1067
-
"type": "integer"
1068
-
}
1069
-
}
1070
-
},
1071
1009
"ServerHealth": {
1072
1010
"type": "object",
1073
1011
"properties": {
@@ -1154,8 +1092,8 @@
1154
1092
}
1155
1093
},
1156
1094
"readinessProbe": {
1157
-
"description": "Settings for the readiness probe associated with a WebLogic Server instance.",
1158
-
"$ref": "#/definitions/ReadinessProbe"
1095
+
"description": "Settings for the readiness probe associated with a WebLogic Server instance. If not specified, the operator will create an HTTP probe accessing the /weblogic/ready path. If an HTTP probe is specified then the operator will fill in `path`, `port`, and `scheme`, if they are missing. The operator will also fill in any missing tuning-related fields if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different HTTP path to access.",
"description": "Container-level security attributes. Will override any matching Pod-level attributes. See `kubectl explain pods.spec.containers.securityContext`. Beginning with operator version 4.0.5, if no value is specified for this field, the operator will use default content for container-level `securityContext`. More info: https://oracle.github.io/weblogic-kubernetes-operator/security/domain-security/pod-and-container/.",
@@ -1177,8 +1115,8 @@
1177
1115
"type": "integer"
1178
1116
},
1179
1117
"livenessProbe": {
1180
-
"description": "Settings for the liveness probe associated with a WebLogic Server instance.",
1181
-
"$ref": "#/definitions/ProbeTuning"
1118
+
"description": "Settings for the liveness probe associated with a WebLogic Server instance. If not specified, the operator will create a probe that executes a script provided by the operator. The operator will also fill in any missing tuning-related fields, if they are unspecified. Tuning-related fields will be inherited from the domain and cluster scopes unless a more specific scope defines a different action, such as a different script to execute.",
"description": "TopologySpreadConstraints describes how a group of pods ought to spread across topology domains. Scheduler will schedule pods in a way which abides by the constraints. All topologySpreadConstraints are ANDed.",
0 commit comments