Container Gateway of pod faas-netes CrashLoopBackOff : Readiness probe failed and Liveness probe failed

[WhaleSpring]

Expected Behaviour

I hope my openfaas in my cluster to be ok.

Current Behaviour

My openfaas was OK 2 weeks ago, but it turns down last week:
Container gateway of pod faas-netes CrashLoopBackOff , with queue-worker alse being CrashLoopBackOff sometimes:

Here are the messages got by kubectl describe pod -n openfaas faas-netes-xxxxx
Warning Unhealthy 43m (x9 over 43m) kubelet Readiness probe failed: Get "http://10.244.104.19:8080/healthz": dial tcp 10.244.104.19:8080: connect: connection refused Warning Unhealthy 14m (x45 over 43m) kubelet Liveness probe failed: Get "http://10.244.104.19:8080/healthz": dial tcp 10.244.104.19:8080: connect: connection refused Warning BackOff 4m45s (x164 over 42m) kubelet Back-off restarting failed container

Here are the logs of container gateway and conatiner faas-netes of pod faas-netes:

Why is this needed?

• I have raised an issue to propose this change (required)

Who is this for?

What company is this for? Are you listed in the ADOPTERS.md file?

List All Possible Solutions and Workarounds

Steps to Reproduce (for bugs)

Context

Your Environment

• FaaS-CLI version ( Full output from: faas-cli version ):
  

• Docker version docker version (e.g. Docker 17.0.05 ):
  Client: Docker Engine - Community
  Version: 20.10.21

• What version and distriubtion of Kubernetes are you using? kubectl version
  1.23.0

• Operating System and version (e.g. Linux, Windows, MacOS):
  CentOS Linux release 7.6.1810 (Core)

• Link to your project or a code example to reproduce issue:

• What network driver are you using and what CIDR? i.e. Weave net / Flannel
  calico

[TYsonHe]

mark it. I have the same problem on my cluster

[WhaleSpring]

It is worth mentioning that this issue also occurred in my newly deployed virtual machine cluster of ubuntu22.04 with k8s v1.28.2 , CRI-O 1.28 and flannel as network component.
/sig network

[WhaleSpring]

It's errors from my network . Not openfaas.

[alexellis]

No problems. We've not experienced any issues over here, so it looks like it's localised to your own environments.

If you're enjoying OpenFaaS, check out how you can support the project back:

https://github.com/sponsors/openfaas/