Skip to content

helm chart minio bug + extension upload bug #2067

@hm2075

Description

@hm2075

Describe the bug

when a user sets up their own instance of minio, gitpod server deployment continues to use hard coded values

update chart/templates/server-deployment.yaml

{{- if eq .Values.components.wsDaemon.remoteStorage.kind "minio" }}
        - name: GITPOD_STORAGE_CLIENT
          value: minio
        - name: MINIO_END_POINT
          value: minio.{{ .Release.Namespace }}.svc.cluster.local
        - name: MINIO_PORT
          value: "9000"
        - name: MINIO_ACCESS_KEY
          value: {{ .Values.minio.accessKey }}
        - name: MINIO_SECRET_KEY
          value: {{ .Values.minio.secretKey }}
        - name: MINIO_REGION
          value: {{ .Values.minio.region }}
    {{- end }}

replacing these hard codes values with those from values.yaml

with a linked issue on uploading extensions, users using minio pod or external minio are unable to upload extensions

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions