Weblogic operator fails to perform rolling restart of managed servers.
Surabhi0709 opened this issue · comments
We are currently using weblogic-kubernetes-operator version :3.3.8
Our application is deployed to a WLS cluster
Problem:
So the whenever a new auxiliary image with the new application binary is deployed the expected behavior is that the WebLogic Kubernetes Operator will do a rolling restart of the individual managed servers to pick up the new version of the application.
However in our case we have observed that the operator is not performing a rolling bounce and the number of active pods drops below 2 causing a potential outage of service for 5-10 mins depending on the number of pods.
Question:
Is there any implementation technique or configuration fields that we can spread out the time period taken by weblogic operator to perform rolling restart of the pods .
@Surabhi0709 just a follow up to our discussions in the slack last week about this issue. Do you still see this issue now?
There's been no response for months. I'm assuming that this issue has been resolved.