-
Notifications
You must be signed in to change notification settings - Fork 218
Owls 103828 - Fix for the Cluster and Domain 'Available' conditions for admin only domains and intentionally shutdown clusters #3602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
a54d759
f8caa67
d3eb72b
1a4ff8d
6f0ca59
f5b93fa
5353805
b395c9d
db92d4a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -195,15 +195,22 @@ The following is a list of condition types for a Cluster resource. | |
* There are no pending server shutdown requests. | ||
|
||
#### `Available` {id="cluster-available"} | ||
- The `status` attribute is set to `True` when a sufficient number of WebLogic Server pods are | ||
ready in the cluster. This includes either: | ||
* All WebLogic Server pods in the cluster are ready, as configured in the `cluster.spec.replicas` field, | ||
or if it is not configured, then in the `domain.spec.replicas` field. | ||
* Some of the expected server pods for the cluster are temporarily not ready, and the number of | ||
`not ready` server pods is less than or equal to `cluster.spec.maxUnavailable` which defaults to `1`. | ||
- The `status` attribute is also set to `True` when no WebLogic Server pods are running and this | ||
is the expected state, such as when `cluster.spec.replicas` is set to `0`, or when | ||
`cluster.spec.serverStartPolicy` is set to `Never`. | ||
- The `status` attribute is set to `True` when a sufficient number of WebLogic Server pods are | ||
ready in the cluster. Both of the following must be true: | ||
- At least one pod in the cluster is expected to run and is `ready`. | ||
- The number of `not ready` server pods which are expected to run | ||
is less than or equal to `cluster.spec.maxUnavailable` which defaults to `1`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is less than or equal to |
||
- Examples: | ||
- If a cluster has `serverStartPolicy` `Never` or `replicas` `0`, | ||
or a cluster is in a domain with `serverStartPolicy` `AdminOnly` or `Never`, | ||
then the cluster will have `Available` `False`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Re-write (I can hardly understand the meaning of this sentence, but here's a stab at it): If a cluster has a |
||
- If a cluster and domain both have a `serverStartPolicy` of `IfNeeded`, | ||
and `cluster.spec.replicas` is `1`, | ||
then the cluster `Available` will be `True` only when its single pod is `ready`. | ||
- If a cluster and domain both have a `serverStartPolicy` of `IfNeeded`, | ||
`cluster.spec.replicas` is `4`, | ||
and `cluster.spec.maxUnavailable` is `1` (the default), | ||
then the cluster `Available` will be `True` only when three or four of its pods are `ready`. | ||
- **Note**: The `Available` `status` can be `True` even when the `status` for the `Completed` | ||
condition is `False`, a `Failed` condition is reported on the Domain resource, or the cluster | ||
has up to `cluster.spec.maxUnavailable` pods that are not ready. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pods which are expected to run -> pods, which are expected to run, (two commas needed)