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

feature: option to add volumes and volumeMounts to minio-operator pod #1700

Merged
merged 2 commits into from
Jul 31, 2023

Conversation

yanehi
Copy link
Contributor

@yanehi yanehi commented Jul 26, 2023

Problem

I want to run my minio instance (operator and console) with the readOnlyRootFilesystem: true option. Unfortunately, this isn't possible for the operator pod, since I don't have an option to mount an emptyDir (like I did with the console pod).

So I'm currently getting the following error:

panic: mkdir /tmp/operator: read-only file system

Solution

As with the console pod, I can now optionally use a volume for the operator pod.

values.yaml

  volumes: [ ]
  volumeMounts: [ ]

operator-deployment.yaml

          {{- with .Values.operator.volumeMounts }}
          volumeMounts: {{- toYaml . | nindent 12 }}
          {{- end }}
      {{- with .Values.operator.volumes }}
      volumes: {{- toYaml . | nindent 8 }}
      {{- end }}

@shtripat shtripat requested a review from pjuarezd July 31, 2023 04:30
@pjuarezd pjuarezd merged commit eb8793a into minio:master Jul 31, 2023
24 checks passed
@yanehi yanehi deleted the feat/add-volumemount-operator branch July 31, 2023 07:16
@cniackz
Copy link
Contributor

cniackz commented Sep 7, 2023

@yanehi what type of data will be stored in that emptyDir that you want to mount?. I am just curious and I want to understand why this is needed?. Then we can document it!.

@feorlen ⬆️

@bh4t bh4t added the enhancement New feature or request label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants