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/staging/content/managing-domains/accessing-the-domain/domain-events.md
+26-11Lines changed: 26 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ description = "Monitor domain resources using operator-generated events about re
9
9
10
10
### Overview
11
11
12
-
This document describes Kubernetes events that the operator generates about resources that it manages, during key points of its processing workflow. These events provide an additional way of monitoring your domain resources. Most of the operator-generated events are associated with a domain resource, and those events are included in the domain resource object as well. Note that the Kubernetes server also generates events for standard Kubernetes resources, such as pods, services, and jobs that the operator generates on behalf of deployed domain custom resources.
12
+
This document describes Kubernetes events that the operator generates about resources that it manages, during key points of its processing workflow. These events provide an additional way of monitoring your domain resources. Most of the operator-generated events are associated with a domain resource, and those events are included in the Domain resource object as well. Note that the Kubernetes server also generates events for standard Kubernetes resources, such as pods, services, and jobs that the operator generates on behalf of deployed domain custom resources.
13
13
14
14
### What's new
15
15
@@ -29,7 +29,11 @@ The domain events have been enhanced in 4.0. Here is a summary of the changes in
29
29
* Have a better failure categorization (see [Operator-generated event types](#operator-generated-event-types) for more details).
30
30
* Include the categorization information in the event message.
31
31
* Provide more information in the event message to indicate what has gone wrong, what you need to do to resolve the problem, and if the operator will [retry]({{< relref "/managing-domains/domain-lifecycle/retry.md" >}}) the failed operation.
32
-
* Added three event types, `Unavailable`, `Incomplete`, and `FailureResolved`, to record the transition of domain condition `Available/Completed/Failed` from `True` to `False`, and vice versa.
32
+
* Added four event types: `Available`, `Unavailable`, `Incomplete`, and `FailureResolved`, to record
33
+
the transition of their corresponding [Domain resource status conditions]({{< relref "/managing-domains/accessing-the-domain/status-conditions#types-of-domain-conditions" >}}).
`ClusterDeleted`, `ClusterIncomplete`, and `ClusterUnavailable`, to record the transition of their
36
+
corresponding [Cluster resource status conditions]({{< relref "/managing-domains/accessing-the-domain/status-conditions#types-of-cluster-conditions" >}}).
33
37
34
38
### Operator-generated event types
35
39
@@ -38,23 +42,34 @@ The operator generates these event types in a domain namespace, which indicate t
38
42
*`Created`: A new domain is created.
39
43
*`Changed`: A change has been made to an existing domain.
40
44
*`Deleted`: An existing domain has been deleted.
41
-
*`Available`: An existing domain is available, which means a sufficient number of servers are ready such that the customer's applications are available.
42
-
*`Failed`: The domain resource encountered a problem which prevented it from becoming fully up. The possible failure could be one or multiple of the following conditions:
43
-
* Invalid configurations in domain resource.
45
+
*`Available`: An existing domain is available, which means that a sufficient number of servers are ready such that the customer's applications are available. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#available" >}}).
46
+
*`Failed`: The domain resource encountered a problem which prevented it from becoming fully up.
47
+
For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#failed" >}}).
48
+
The possible failure could be one or more of the following conditions:
49
+
* Invalid configurations in the domain resource.
44
50
* A Kubernetes API call error.
45
51
* Introspection failures.
46
52
* An unexpected error in a server pod.
47
-
* A topology mismatch between the domain resource configuration and the WebLogic domain configuration.
48
-
* The replicas of a cluster in the domain resource exceeds the maximum number of servers configured for the WebLogic cluster.
53
+
* A topology mismatch between the Domain resource configuration and the WebLogic domain configuration.
54
+
* The replicas of a cluster in the Domain resource exceeds the maximum number of servers configured for the WebLogic cluster.
49
55
* An internal error.
50
56
* A failure that retries will not help, or has been retried and has exceeded the [pre-defined maximum retry time]({{< relref "/managing-domains/domain-lifecycle/retry#retry-behavior" >}}).
51
57
*`Completed`: The domain resource 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.all servers that are supposed to be started are up running.
52
-
*`Unavailable`: The domain resource is unavailable, which means the domain does not have a sufficient number of servers active.
58
+
For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#completed" >}}).
59
+
*`Unavailable`: The domain resource is unavailable, which means that the domain does not have a sufficient number of servers active. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#available" >}}).
53
60
*`Incomplete`: The domain resource is incomplete for one or more of the following reasons: there are failures detected, there are pending server shutdowns, or not all servers expected to be running are ready and at their target image, auxiliary images, restart version, and introspect version.
54
-
*`FailureRessolved`: The failure condition that the domain was in has been resolved.
61
+
For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#completed" >}}).
62
+
*`FailureResolved`: The failure condition that the domain was in, has been resolved. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#failed" >}}).
55
63
*`RollStarting`: The operator has detected domain resource or Model in Image model
56
-
updates that require it to perform a rolling restart of the domain.
57
-
*`RollCompleted`: The operator has successfully completed a rolling restart of a domain.
64
+
updates that require it to perform a rolling restart of the domain. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#rolling" >}}).
65
+
*`RollCompleted`: The operator has successfully completed a rolling restart of a domain. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#rolling" >}}).
66
+
*`ClusterCreated`: A new Cluster resource is created.
67
+
*`ClusterChanged`: A change has been made to an existing Cluster resource.
68
+
*`ClusterDeleted`: An existing Cluster resource has been deleted.
69
+
*`ClusterAvailable`: An existing cluster is available, which means that a sufficient number of its servers have reached the ready state. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#cluster-available" >}}).
70
+
*`ClusterCompleted`: The cluster 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. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#cluster-completed" >}}).
71
+
*`ClusterIncomplete`: The cluster is incomplete for one or more of the following reasons: there are failures detected, there are pending server shutdowns, or not all servers expected to be running are ready and at their target image, auxiliary images, restart version, or introspect version. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#cluster-completed" >}}).
72
+
*`ClusterUnavailable`: The cluster is unavailable because an insufficient number of its servers that are expected to be running are ready. For details, see the corresponding [condition]({{< relref "/managing-domains/accessing-the-domain/status-conditions#cluster-available" >}}).
58
73
*`PodCycleStarting`: The operator has started to replace a server pod after it detects that the current pod does not conform to the current domain resource or WebLogic domain configuration.
59
74
*`NamespaceWatchingStarted`: The operator has started watching for domains in a namespace.
60
75
*`NamespaceWatchingStopped`: The operator has stopped watching for domains in a namespace. Note that the creation of this event in a domain namespace is the operator's best effort only; the event will not be generated if the required Kubernetes privilege is removed when a namespace is no longer managed by the operator.
0 commit comments