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
We've experienced this issue too, and the quick answer is that this is a configuration issue with your K8s cluster.
Looking at your logs, the liveness probe URL is being accessed from your WAN interface on a node.
The access control rules for the liveness probe endpoint in this wordpress-runtime image reject access from outside the cluster private subnet of 10.0.0.0/8. You can override this CIDR by setting the STATS_WHITELIST_CIDR env variable (it appears). Here's where this gets applied to the nginx configuration:
We're waiting to hear back from our service provider (Linode / LKE) to see what can be done at their end. I'd suggest doing the same, or looking at your routing table on nodes.
Suggest this issue gets closed, as it's not a bug in bitpoke/stack-runtimes.
The WordPress pod crashes because the readiness probe fails to ping the nginx server. I get the following error.
Expect
WordPress to run without crashing.
Reproduce
Create WordPress CRD on kubernetes using wordpress operator.
Below is the full log.
The text was updated successfully, but these errors were encountered: