search

drupalwxt / helm-drupal

Helm Chart for deploying an enterprise-grade Drupal environment.
https://drupalwxt.github.io/helm-drupal/index.yaml
MIT License
31 stars 22 forks source link

Issue deploying the chart #33

Closed bmaltais closed 4 years ago

bmaltais commented 4 years ago

I am trying to deploy the chart with:

kubectl create namespace drupal-wxt
helm install drupal-wxt --namespace gocweb -f values.yaml --wait .

but I am getting the following error:

helm install drupal-wxt --namespace gocweb -f values.yaml --wait .
Error: template: drupal/charts/minio/templates/deployment.yaml:210:20: executing "drupal/charts/minio/templates/deployment.yaml" at <(not .Values.gcsgateway.enabled) (not .Values.azuregateway.enabled) (not .Values.s3gateway.enabled) (not .Values.b2gateway.enabled)>: can't give argument to non-function not .Values.gcsgateway.enabled

Look like it is possibly related to minio?

bmaltais commented 4 years ago

More info. I found this reference to an issue with the minio template and new version of go: https://community.gitpod.io/t/issues-installing-on-own-k8/1531/5

Not sure what is the relation between them yet... go is not installed on my devcontainer... so not sure why this is an issue.

bmaltais commented 4 years ago

More update. I was able to fix the issue by updating the version of minio being deployed to 6.0.5. Look like the old 5.0.x release is not compliant with new version of helm due to golan validation:

dependencies:
  - name: mysql
    version: 1.6.2
    repository: https://kubernetes-charts.storage.googleapis.com
    condition: mysql.enabled
  - name: minio
    version: 6.0.5
    repository: https://helm.min.io/
    condition: minio.enabled
  - name: postgresql
    version: 8.6.4
    repository: https://kubernetes-charts.storage.googleapis.com
    condition: postgresql.enabled
  - name: varnish
    version: 0.0.2
    repository: https://statcan.github.io/charts
    condition: varnish.enabled
sylus commented 4 years ago

Hey @bmaltais thanks so much for finding this and sorry caused issues.

Especially since we at least ourselves are more using Azure Files (NFS) for the shared mounts without needing the minio deployment and Drupal logic for handling s3.

sylus commented 4 years ago

I pushed your fix up and really appreciate you taking the time, and apologies for the delay.