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
As part of our resiliency testing to test liveness and readiness probe for OPA container, we intentionally made the OPA container down which resulted in the restart of OPA container. When the OPA container came back there was an error seen in OPA container logs "error": { "code": "undefined_document", "message": "document missing: data.system.main" },
This is because kube-mgmt didn't reload the policies to OPA as it couldn't identify that OPA container restarted.
As a result of this we are seeing below error in other application logs
failed calling webhook "[mutating-webhook.openpolicyagent.org](http://mutating-webhook.openpolicyagent.org/)"
kube-mgmt should be able to identify the restarts of OPA container and reload the policies to avoid hitting this issue.
The text was updated successfully, but these errors were encountered:
Hi,
As part of our resiliency testing to test liveness and readiness probe for OPA container, we intentionally made the OPA container down which resulted in the restart of OPA container. When the OPA container came back there was an error seen in OPA container logs
"error": { "code": "undefined_document", "message": "document missing: data.system.main" },
This is because kube-mgmt didn't reload the policies to OPA as it couldn't identify that OPA container restarted.
As a result of this we are seeing below error in other application logs
failed calling webhook
"[mutating-webhook.openpolicyagent.org](http://mutating-webhook.openpolicyagent.org/)"
kube-mgmt should be able to identify the restarts of OPA container and reload the policies to avoid hitting this issue.
The text was updated successfully, but these errors were encountered: