Fix for "stuck" operator when its informers have disconnected

If there is a networking issue for your node or cluster, you
may find the operator's informers disconnect. You'd see an
error if that happened. This will now be reported through
the health endpoint so that Kubernetes can restart the
container.

This is a rare error, but can be non-obvious to spot. See
the customer community discussions for more.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

chart/openfaas/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 type: application
 description: OpenFaaS - Serverless Functions Made Simple
 name: openfaas
-version: 14.2.97
+version: 14.2.98
 sources:
 - https://github.com/openfaas/faas
 - https://github.com/openfaas/faas-netes

chart/openfaas/values.yaml

@@ -154,7 +154,7 @@ eventWorker:
 
 # For OpenFaaS Pro and the Function CRD
 operator:
-  image: ghcr.io/openfaasltd/faas-netes:0.5.63
+  image: ghcr.io/openfaasltd/faas-netes:0.5.64
   create: false
   logs:
     debug: false
@@ -201,7 +201,7 @@ operator:
     successThreshold: 1
 
 faasnetesPro:
-  image: ghcr.io/openfaasltd/faas-netes:0.5.63
+  image: ghcr.io/openfaasltd/faas-netes:0.5.64
   logs:
     debug: false
     format: "console"