Gatekeeper upgrade retries exhausted

Bug

Description

Describe the problem, what were you doing when you noticed the bug?

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

After multiple times start & restart the Flux components, kustomize-controller, helm-controller, source-controller & notification-controller Gatekeeper reconciliation given an error upgrade retries exhausted. I see the following errors,

Controller: kustomize-controller Namespace: flux-system

connect: connection refused Readiness probe failed: Get "http://xx.xx.xx.xxx:9090/readyz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Warning Unhealthy Liveness probe failed: Get "http://xx.xx.xx.xxx:9090/healthz": dial tcp 10.2.32.153:9090:

Readiness probe failed: HTTP probe failed with statuscode: 500 node-controller Node is not ready Back-off restarting failed container

Pod: gatekeeper-audit Namespace: gatekeeper-system "msg":"networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress\n"}

BigBang Version

What version of BigBang were you running? 1.19.0

This can be retrieved multiple ways: Yes

# via helm
helm ls -n bigbang

# via the deployed umbrella git tag
kubectl get gitrepository -n bigbang