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
@tomazzaman sorry i cannot find the locs where you implement the /healthz entry on the php code, can you please point me there? thanks 👍 👴 I hold the 🔑 he he.
The text was updated successfully, but these errors were encountered:
There are differences between the image generated in the tutorials and the one available from codeable/kubepress:4.8.1 ... the latter image configures the /healthz endpoint in /etc/nginx/conf.d/default.conf, not via wordpress.
# Health check for Kubernetes readiness probe
location /healthz {
access_log off;
return 200;
}
This may be a necessary workaround because Ingress doesn't allow any traffic through to the backend service until the service returns a 200 from an endpoint, but WordPress always returns a 301 (permanent redirect) if the host header of a request doesn't match the configured site url, so the service is never considered 'healthy' when wordpress is allowed to answer the health-check.
@tomazzaman sorry i cannot find the locs where you implement the /healthz entry on the php code, can you please point me there? thanks 👍 👴 I hold the 🔑 he he.
The text was updated successfully, but these errors were encountered: