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

[bitnami/minio]Console web ui creating Access Keys failed, this causes the pod to restarted. #25882

Open
yeahfo opened this issue May 15, 2024 · 3 comments
Assignees
Labels
in-progress minio tech-issues The user has a technical issue about an application

Comments

@yeahfo
Copy link

yeahfo commented May 15, 2024

Name and Version

bitnami/minio 14.4.2

What architecture are you using?

amd64

What steps will reproduce the bug?

My helmfile yaml

repositories:
  - name: bitnami
    url: https://charts.bitnami.com/bitnami
releases:
  - name: minio
    chart: bitnami/minio
    version: 14.4.2
    values:
      - service:
          type: NodePort
          nodePorts:
            api: "30900"
            console: "30901"
      - auth:
          rootUser: admin
          rootPassword: adminpwd
      - persistence:
          enabled: false
  • Login to console web ui.
  • Click the Access Keys menu.
  • Create access key.
  • Continuing to refresh the browser after a failed creation will cause the pod to restart continuously.

What do you see instead?

Error and Access key is not created.

@yeahfo yeahfo added the tech-issues The user has a technical issue about an application label May 15, 2024
@github-actions github-actions bot added the triage Triage is needed label May 15, 2024
@yeahfo yeahfo changed the title Console web ui creating Access Keys failed, this causes the pod to restarted. [bitnami/minio]Console web ui creating Access Keys failed, this causes the pod to restarted. May 15, 2024
@github-actions github-actions bot removed the triage Triage is needed label May 17, 2024
@github-actions github-actions bot assigned jotamartos and unassigned carrodher May 17, 2024
@jotamartos
Copy link
Contributor

Hi @yeahfo,

Thank you for reporting this issue. I just checked that it's related to the resources assigned to the pod and the container. You can read more about how to modify this here

https://github.com/bitnami/charts/tree/main/bitnami/minio#resource-requests-and-limits

If you increase the resources, the application will be more stable. You can suggest a change for the default value by following our contributing guidelines.

@yeahfo
Copy link
Author

yeahfo commented May 21, 2024

Hi @yeahfo,

Thank you for reporting this issue. I just checked that it's related to the resources assigned to the pod and the container. You can read more about how to modify this here

https://github.com/bitnami/charts/tree/main/bitnami/minio#resource-requests-and-limits

If you increase the resources, the application will be more stable. You can suggest a change for the default value by following our contributing guidelines.

Thank you @jotamartos ,
Can you give me some advice? For example: helm/helmfile... --set resources.? =?

@jotamartos
Copy link
Contributor

Hi @yeahfo,

As the values.yaml states, you can use many different values for that parameter (nano, micro, small, ...)

https://github.com/bitnami/charts/blob/main/bitnami/minio/values.yaml#L620

You can try with small and use a higher value if needed

helm install minio --set resourcesPreset="small" bitnami/minio

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in-progress minio tech-issues The user has a technical issue about an application
Projects
None yet
Development

No branches or pull requests

3 participants