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
If the OPA HTTP server is only listening on localhost the kubelet cannot execute HTTP health checks against the Health API. You can reproduce this problem simply by deploying OPA with --addr=127.0.0.1:8181. If you enable liveness and readiness probes the pod will fail to start because the kubelet can't connect to the HTTP server.
The current workaround is to tell OPA to bind on 0.0.0.0 instead of localhost.
There are a couple ways this could be addressed:
Add support for serving the Health API on another address/port
Add a subcommand into the OPA binary to execute a health check (then the kubelet can use execProbe)
The text was updated successfully, but these errors were encountered:
This adds a new config option for the OPA server (along with plumbing
from `opa run` downward to the server) to configure separate
diagnostic addresses to listen on. These will only be configured to
serve the /metrics and /health.
This will allow for more secure OPA deployments with the normal "data"
or "policies" API's made to be only accessible on localhost.
Fixes: open-policy-agent#2002
Signed-off-by: Patrick East <east.patrick@gmail.com>
This adds a new config option for the OPA server (along with plumbing
from `opa run` downward to the server) to configure separate
diagnostic addresses to listen on. These will only be configured to
serve the /metrics and /health.
This will allow for more secure OPA deployments with the normal "data"
or "policies" API's made to be only accessible on localhost.
Fixes: #2002
Signed-off-by: Patrick East <east.patrick@gmail.com>
If the OPA HTTP server is only listening on localhost the kubelet cannot execute HTTP health checks against the Health API. You can reproduce this problem simply by deploying OPA with
--addr=127.0.0.1:8181
. If you enable liveness and readiness probes the pod will fail to start because the kubelet can't connect to the HTTP server.The current workaround is to tell OPA to bind on 0.0.0.0 instead of localhost.
There are a couple ways this could be addressed:
The text was updated successfully, but these errors were encountered: