When WKO (WebLogic Kubernetes Operator) Pod is Stopped The "ResourceQuotas" of WebLogic Domain Namespace are Increased then Fail to Launch New Pods
(Doc ID 3050567.1)
Last updated on OCTOBER 04, 2024
Applies to:
Oracle WebLogic Server - Version 12.2.1.4.0 to 14.1.1.0.0 [Release 12c to 14c]Information in this document applies to any platform.
Symptoms
When WKO Pod is Stopped, the ResourceQuotas of WebLogic Domain Namespace are Increased Then fail to Launch New Pods
When weblogic-operator pod is stopped (shutdown), ResourceQuotas of the WebLogic domain namespace is increased.
When WebLogic server pods are also restarted at the same time, these pods are not started due to exceeding resource quota.
weblogic-operator pod is shutdown using the following delete command.
kubectl -n <OPERATOR_NAMESPACE> delete pods weblogic-operator-<ID> weblogic-operator-webhook-<ID>
Changes
Shutdown weblogic-operator pod
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |