search

gravitee-io / issues

Gravitee.io - API Platform - Issues
65 stars 26 forks source link

[helm] Chart 3.1.35 : mongodb replicaset no more deployed compared to previous version 3.1.32 #7478

Closed apoddany closed 2 years ago

apoddany commented 2 years ago

:collision: Describe the bug

When trying to deploy helm charts with Chart version 3.1.35, mongodb replicaset are no more deployed They are correctly deployed with 3.1.32.

:sunrise_over_mountains: To Reproduce

Steps to reproduce the behaviour:

  1. In K8s (here Minikube was used), create apim-core directory and add the 2 attached files
% helm repo add graviteeio https://helm.gravitee.io

% vi apim-core/Chart.yaml (set to 3.1.35)

% helm dependency update apim-core

% ls apim-core/charts
-rw-r--r--  1 apoddany  staff  81814  7 avr 15:38 apim3-3.1.35.tgz

% helm install apim-core-local --namespace apim-core-local -f apim-core/values_gravitee.yaml apim-core

% kubectl get pods --namespace apim-core-local
NAME                        READY   STATUS    RESTARTS   AGE
apim-api-58b9565448-q225s   0/1     Pending   0          50s
  1. No entry for the mongodb replicaset pods
  2. Now set it to 3.1.32 : 
% helm uninstall apim-core-local --namespace apim-core-local
release "apim-core-local" uninstalled

% kubectl get pods --namespace apim-core-local
No resources found in apim-core-local namespace.

% vi apim-core/Chart.yaml (set to 3.1.32)

% helm dependency update apim-core

% ls apim-core/charts/a*
-rw-r--r--  1 apoddany  staff  158397  7 avr 16:08 apim3-3.1.32.tgz

% helm install apim-core-local --namespace apim-core-local -f apim-core/values_gravitee.yaml apim-core

% kubectl get pods --namespace apim-core-local
NAME                                   READY   STATUS    RESTARTS   AGE
apim-api-5fb95b4f76-t5ph4              0/1     Pending   0          3m58s
apim-core-local-mongodb-replicaset-0   1/1     Running   0          3m58s
apim-core-local-mongodb-replicaset-1   0/1     Pending   0          3m37s
  1. mongodb replicaset pods are present

:rainbow: Expected behaviour

A clear and concise description of what you expected to happen.

Current behaviour

A clear and concise description of what is currently happening.

:movie_camera: Useful information

Screenshot, video, logs, other supporting material Archive.zip

:computer: Desktop:

Please complete the following information:

:warning: Potential impacts

Which other features may be impacted by this fix. This could be populated after fix

What are the impacted versions?

:link: Dependencies

Link a story or other related things...

apoddany commented 2 years ago

closing as :

It sounds like an issue with the MongoDB Helm Chart introduced by this particular commit https://github.com/helm/charts/commit/79190dbf2ecd1b3b214561a8a48a14f02459b35f#diff-a5278149ee6f9c7573a1d34a447b63ecf43fde2d8d0e9e777495952ced01f8dbR210 SuccessThreshold can't be 2 and so pod are not starting.

For the time being, can you please update your values with this:

   mongodb-replicaset:
    enabled: true
    startupProbe:
      initialDelaySeconds: 5
      timeoutSeconds: 5
      failureThreshold: 60
      periodSeconds: 10
      successThreshold: 1

We are looking at upgrading mongodb and elasticsearch dependencies soon.