Minio Ingress Probleme

[pomland-94]

trafficstars

Name and Version

bitnami/minio:latest

What architecture are you using?

arm64

What steps will reproduce the bug?

1. On Premise Kubernetes Cluster
2. ingress-nginx Controller

Are you using any custom parameters or values?

global:
  storageClass: "rook-cephfs"
mode: distributed
auth:
  ## @param auth.rootUser MinIO® root username
  ##
  rootUser: admin
  ## @param auth.rootPassword Password for MinIO® root user
  ##
  rootPassword: "Test2024"
  ## @param auth.existingSecret Use existing secret for credentials details (`auth.rootUser` and `auth.rootPassword` will be ignored and picked up from this secret). The secret has to contain the keys `root-user` and `root-password`)
  ##
  existingSecret: ""
  useCredentialsFiles: false
  forceNewKeys: false
disableWebUI: false
tls:
  enabled: false
  autoGenerated: false
  existingSecret: ""
provisioning:
  enabled: true
  resourcesPreset: "medium"
  buckets:
    - name: artifacts
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc
    - name: external-diffs
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: uploads
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: lfs
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: packages
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: dependency-proxy
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: terraform-state
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: pages
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
    - name: ci-secure-files
      versioning: Versioned
      quota:
        type: set
        size: 20GiB
      region: de-nbg1-dc3
  config:
    - name: region
      options:
        name: de-nbg1-dc3
  containerSecurityContext:
    enabled: true
    runAsUser: 1001
    runAsGroup: 1001
    runAsNonRoot: true
    privileged: false
    readOnlyRootFilesystem: true
    allowPrivilegeEscalation: false
    capabilities:
      drop: ["ALL"]
    seccompProfile:
      type: "RuntimeDefault"
containerSecurityContext:
  enabled: true
  seLinuxOptions: {}
  runAsUser: 1001
  runAsGroup: 1001
  runAsNonRoot: true
  privileged: false
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
  seccompProfile:
    type: "RuntimeDefault"
resourcesPreset: "medium"
ingress:
  enabled: true
  ingressClassName: "nginx"
  hostname: minio.contentways.org
  path: /console
  pathType: ImplementationSpecific
  servicePort: minio-console
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
    cert-manager.io/cluster-issuer: default-clusterissuer
  tls: true
  selfSigned: false
apiIngress:
  enabled: true
  ingressClassName: "nginx"
  hostname: minio.contentways.org
  path: /
  pathType: ImplementationSpecific
  servicePort: minio-api
  annotations:
    cert-manager.io/cluster-issuer: default-clusterissuer
  tls: true
  selfSigned: false
persistence:
  enabled: true
  storageClass: "rook-cephfs"
  mountPath: /bitnami/minio/data
  accessModes:
    - ReadWriteMany
  size: 100Gi
metrics:
  prometheusAuthType: public
  serviceMonitor:
    enabled: false
  prometheusRule:
    enabled: false

What is the expected behavior?

No response

What do you see instead?

When i try to open https://minio.contentways.org/console The Static Ressources are not loaded.

Additional information

No response

[carrodher]

The issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a specific scenario that is not easy to reproduce on our side.

If you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.

With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.

[pomland-94]

But what can be the error? My Ingress Nginx is Correctly Deployed...

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.