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
Currently, the kong-proxy service doesn't expose port 8100 that is used for status checks but pods do expose the same port.
To be able to use dataplane running in a cloud provider, this is a must because loadbalancers/gateways are often. configured to perform healthchecks on certain routes and currently that is not possible.
Only workaround is to create another service as part of the extraObjects block in Helm chart values.yaml that exposes port 8100.
It would be nice no to have to define custom service resource and rely on chart itself to provide proper way for reaching /status/ready endpoint.
The text was updated successfully, but these errors were encountered:
Currently, the kong-proxy service doesn't expose port 8100 that is used for status checks but pods do expose the same port.
To be able to use dataplane running in a cloud provider, this is a must because loadbalancers/gateways are often. configured to perform healthchecks on certain routes and currently that is not possible.
Only workaround is to create another service as part of the
extraObjects
block in Helm chart values.yaml that exposes port 8100.It would be nice no to have to define custom service resource and rely on chart itself to provide proper way for reaching
/status/ready
endpoint.The text was updated successfully, but these errors were encountered: