Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minio helm chart related issues, always using default namespace #175

Open
cftang0827 opened this issue Feb 4, 2025 · 0 comments
Open

Minio helm chart related issues, always using default namespace #175

cftang0827 opened this issue Feb 4, 2025 · 0 comments

Comments

@cftang0827
Copy link

Hi there,
I got some issuese when I was going to install milvus standalone, but sine it's from minio, therefore not really sure here is the proper place to ask.

When I tried to install milvus standalone version with helm chart, I got the issue, here is my values.yaml setup. (For minio part)

    minio:
        enabled: true
        mode: standalone

And I got an error in k8s side,

Pods "milvus-standalone-minio-74d96b99f9-" is forbidden: error looking up service account default/milvus-standalone-minio: serviceaccount "milvus-standalone-minio" not found:Deployment does not have minimum availability.

Seems like system tried to install minio in default namespace, however, I was using milvus namespace. And the service account had been installed into milvus namespace.

And I looked into the source code of the helm chart (minio part)
helm chart version: 8.0.17

  • deployment.yaml
apiVersion: {{ template "minio.deployment.apiVersion" . }}
kind: Deployment
metadata:
  name: {{ template "minio.fullname" . }}
  labels:
    app: {{ template "minio.name" . }}
    chart: {{ template "minio.chart" . }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
{{- if .Values.additionalLabels }}
{{ toYaml .Values.additionalLabels | trimSuffix "\n" | indent 4 }}
{{- end }}
{{- if .Values.additionalAnnotations }}
  annotations:
{{ toYaml .Values.additionalAnnotations | trimSuffix "\n" | indent 4 }}
{{- end }}
  • serviceaccount.yaml
{{- if .Values.serviceAccount.create -}}
apiVersion: v1
kind: ServiceAccount
metadata:
  name: {{ include "minio.serviceAccountName" . | quote }}
  namespace: {{ .Release.Namespace | quote }}
  labels:
    app: {{ template "minio.name" . }}
    chart: {{ template "minio.chart" . }}
    release: "{{ .Release.Name }}"
{{- end -}}

Looks like there's NO setup of namespace for minio in deployment.yaml but there's namespace setup in serviceaccount.yaml, is that normal?

I guess maybe that's why it cannot find such service account when installing milvus in different namespace.

Thanks.

@cftang0827 cftang0827 changed the title Minio helm chart related issues Minio helm chart related issues, always using default namespace Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant