[Kubernetes] Pods are not recovering on restart - Githubissues

gravitee-io / issues

Gravitee.io - API Platform - Issues

64 stars 26 forks source link

[Kubernetes] Pods are not recovering on restart #4719

Open Andy2003 opened 3 years ago

Andy2003 commented 3 years ago

In case the kubernetes is stopped and re-started the Pods for API and Gateway do not recover.

Expected Behavior

Cluster recovers correctly

Current Behavior

Pods for :

graviteeio-apim3x-api
graviteeio-apim3x-gateway

are not recovering

Possible Solution

I guess the health check is not correctly

Steps to Reproduce (for bugs)

setup minikube
run minikube start
run helm install graviteeio-apim3x graviteeio/apim3 and wait for cluster to come up
run minikube stop and wait for stop
run minikube start and wait for cluster to come up

The Pods for API and Gateway will stay in state Terminated:Error with the Logs saying that the container was shut down.

Your Environment

Version used: helm chart from master (3.x)
Gravitee:
- graviteeio/apim-gateway:3.3.3
- graviteeio/apim-management-api:3.3.3
Operating System and version: Ubuntu 20.4

Andy2003 commented 3 years ago

btw. deleting the pods will create new ones and the cluster will recover afterwards