search

gravitee-io / issues

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

incompatible types error when helm installing #5283

Closed elijahomolo closed 3 years ago

elijahomolo commented 3 years ago

I've run the following using helm 3 as per the installation docs:

helm repo add graviteeio https://helm.gravitee.io
helm install graviteeio-apim3x graviteeio/apim3

The installation fails with:

Error: template: apim3/templates/gateway/gateway-deployment.yaml:53:13: executing "apim3/templates/gateway/gateway-deployment.yaml" at <ne .Values.gateway.image.tag "nightly">: error calling ne: incompatible types for comparison

kubernetes version 1.20.2

Am I missing something in the installation?

TomSearcher commented 3 years ago

Same issue here. Did you find a workaround? Thx

ghabarid commented 3 years ago

Same issue her!

brasseld commented 3 years ago

Hi there,

I'v just published a new version of the chart (3.1.4) which is fixing this issue.

Sorry for the inconvenience.

Regards,

ghabarid commented 3 years ago

Hi, Thx for ur quick answer. The downloaded version works fine. Alle the pods started fine, except the api. It complains about elastic, even though I had disabled it, at es.enable: false; and es.enable: false; elasticsearch.enable: false; The error: vert.x-eventloop-thread-0] ERROR i.g.e.client.http.HttpClient - Unable to get a connection to Elasticsearch: failed to resolve 'graviteeio-apim-elasticsearch-client.default.svc.cluster.local' after 2 queries Is it a misunderstood?

brasseld commented 3 years ago

Hi,

Yea, the management API is requiring a connection to an ES. As you disable embedded ES from the chart, there is no way for the Mgmt-api to gain an access to ES. Reason why you are getting this log.

ghabarid commented 3 years ago

Super, And I guess it s the same for Mongodb. We need to have an instance running, no way for in memory (test) db?

brasseld commented 3 years ago

No, unfortunately there is no way for in-memory db at this time.

MLukman commented 3 years ago

This issue still happens with 3.1.27