search

rudderlabs / rudderstack-helm

Open-source, warehouse-first Customer Data Pipeline and Segment-alternative. Collects and routes clickstream data and builds your customer data lake on your data warehouse.
MIT License
61 stars 48 forks source link

Issue on GKE install #10

Closed jalberto closed 4 years ago

jalberto commented 4 years ago

Using basic install command with helm get:

Error: apiVersion 'v2' is not valid. The value must be "v1"

probably because https://github.com/rudderlabs/rudderstack-helm/blob/b7d613d0c63c70fbe9f838c9da21b6568eee29c8/templates/_helpers.tpl#L81

And becuase GKE doesn't follow Semver: GitVersion:"v1.15.9-gke.24"

Helm version:

Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
jalberto commented 4 years ago

I was wrong, it's because Chart.yaml is set to apiVersion: v2 so the chart seems created with Helm-3, but the templates looks like Helm-2. it's also set in the included transformer chart, downgrading it to v1 seems to do the trick

snarkychef commented 4 years ago

Our charts are built and tested for Helm3. So, apiversion is set to 2. Why do you say that templates look like Helm-2?

harshmanvar commented 4 years ago

i have deployed GKE but getting 404 when opening loadbalancer IP. i have used the example : https://github.com/rudderlabs/rudderstack-helm/blob/master/workspaceConfig.json.example for WorkSpaceConfig.json .

helm chart deployed successfully after changing v2 but still on load balancer IP getting 404

snarkychef commented 4 years ago

We don't have endpoint for / in rudder-server. That might be reason you are getting 404 not found. Please try /health to verify if dataplane is up and running.

snarkychef commented 4 years ago

Closing this issue as discussion going on differs from the original issue.