kubeclarity-grype-server not starting up

[andreifloreavv]

What happened:

Restarted kubeclarity-kubeclarity-grype-server deployment. The grype server pod continuously fails its readiness probe. I've got it installed on a bunch of clusters, but on 2 of them, the pod is just not starting up after a node (instance) refresh.

What you expected to happen:

kubeclarity-kubeclarity-grype-server pod to start up.

How to reproduce it (as minimally and precisely as possible):

AWS EKS node refresh, k8s schedules the pod on a node, but the pod does not start up. Deployment restart does not help.

Are there any error messages in KubeClarity logs?

(e.g. kubectl logs -n kubeclarity --selector=app=kubeclarity)
I've tried enabling the debug logs, but all they say it that the healthz endpoint is starting up.

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version --short): 1.28
• Helm version (use helm version): v3.14.4+g81c902a
• KubeClarity version (use kubectl -n kubeclarity exec deploy/kubeclarity -- ./backend version) v2.23.1
• KubeClarity Helm Chart version (use helm -n kubeclarity list) v2.23.1
• Cloud provider or hardware configuration: AWS EKS
• Others: The application is installed using ArgoCD, with kustomize (v5.2.1 2023-10-19T20:13:51Z) that uses the helm chart.