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

Editing pools not possible with multiple pools #1951

Closed
allanrogerr opened this issue Jan 24, 2024 · 0 comments · Fixed by #1953 · May be fixed by allanrogerr/operator#49
Closed

Editing pools not possible with multiple pools #1951

allanrogerr opened this issue Jan 24, 2024 · 0 comments · Fixed by #1953 · May be fixed by allanrogerr/operator#49
Assignees

Comments

@allanrogerr
Copy link
Contributor

When multiple pools are enabled in a MinIO tenant, editing and saving is not possible through the MinIO Operator Console.

Expected Behavior

Editing pools should be possible.

Current Behavior

1.- The system complains about missing fields
image

2.- Even when these fields are manually populated in the tenant yaml, saving has no effect - as if the button were disabled.

    securityContext:
      fsGroup: 1000
      fsGroupChangePolicy: Always
      runAsGroup: 1000
      runAsNonRoot: true
      runAsUser: 1000

Possible Solution

Modify MinIO Operator Console to pass an empty securityContext when none is found in the pool.

Steps to Reproduce (for bugs)

Create a tenant
Add a pool, ensuring multiple pools are present
Attempt to edit and save any pool
Observe the edit fail as described above

Context

Edit a tenant pool to modify its security context, for example

Regression

Unknown

Your Environment

  • Version used (minio-operator): v5.0.11
  • Environment name and version (e.g. kubernetes v1.17.2): kubectl version Client Version: v1.28.6 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.28.6
  • Server type and version: minio/minio:RELEASE.2024-01-18T22-51-28Z
  • Operating System and version (uname -a): ubuntu linux 23.04
  • Link to your deployment file:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant