You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when i set the MINIO_BROWSER_REDIRECT_URL env, it should take effect and change the shareable link in the console
Current Behavior
when setting the MINIO_BROWSER_REDIRECT_URL in the helm chart config secret or the kustomization tenant env part or a kustomize config secret it will not take effect in the console
i tried it with different image versions and different approaches to set the env
downgrade to a running version (i haven't found one, can someone maybe point me to a running version for MINIO_BROWSER_REDIRECT_URL)
if the problem lies within the console, can i somehow downgrade the console or set the env in another way?
Steps to Reproduce (for bugs)
apply version 2023-11-15 with helm chart or kustomization
login
upload a file
try to share it
have a look at the sharable link, which looks like this for me https://minio.my-sys.svc.cluster.local/hello/world/Screenshot%202023-11-21%20at%2004.17.06.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=2FAHQ8000OLBM2QU6DO2%2F20231124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231124T062642Z&X-Amz-Expires=604800&X-Amz-Security-Token=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiIyRkFIUTgwMDBPTEJNMlFVNkRPMiIsImV4cCI6MTcwMDg1MDA5MSwicGFyZW50IjoiY29uc29sZSJ9.4KzSELvaSRvQXO1mmOXpKzHFgeutK50DVuuisvC2SclnESq5FNkKyFyd9hmBgGQlIOzgBOLf5btWLjYiynmwyA&X-Amz-SignedHeaders=host&versionId=6ff09fa2-d5e2-4b95-b734-30d29c9df764&X-Amz-Signature=8e059c7f6e4109bc235cd9ce2b9e7268f1f4552cd3eaba4f102d1633b7f79acc but should look like this https://minio-console.my-domain.io ...
Context
i want to provide a shareable file link to the user so that he can display/download a file from minio
i tried some different approaches in the secret cfg to set the env (with quotationmarks, without, with single ones), but nothing was taking effect
Regression
RELEASE.2023-11-15T20-43-25Z
Your Environment
Version used (minio-operator): v5.0.11
Environment name and version (e.g. k3s v1.26.4+k3s1):
Server type and version: hetzner hcloud cpx51
Operating System and version (uname -a): ubuntu 22.04
apiVersion: minio.min.io/v2kind: Tenantmetadata:
name: ven-minionamespace: my-sys## Optionally pass labels to be applied to the statefulset podslabels:
app: minio## Optionally pass annotations to be applied to the statefulset podsannotations:
prometheus.io/path: /minio/v2/metrics/clusterprometheus.io/port: "9000"prometheus.io/scrape: "true"## If a scheduler is specified here, Tenant pods will be dispatched by specified scheduler.## If not specified, the Tenant pods will be dispatched by default scheduler.# scheduler:# name: my-custom-schedulerspec:
features:
## Enable S3 specific features such as Bucket DNS which would allow `buckets` to be## accessible as DNS entries of form `<bucketname>.minio.namespace.svc.cluster.local`## This feature is turned off by defaultbucketDNS: true## Specify a list of domains used to access MinIO and Consoledomains: { }## Enable access via SFTP## This feature is turned off by default# enableSFTP: false## Create users in the Tenant using this field. Make sure to create secrets per user added here.## Secret should follow the format used in `minio-creds-secret`.users:
- name: ven-minio-user-console## Create buckets using the console user# buckets:# - name: "test-bucket1"# region: "us-east-1"# objectLock: true# - name: "test-bucket2"# region: "us-east-1"# objectLock: true## This field is used only when "requestAutoCert" is set to true. Use this field to set CommonName## for the auto-generated certificate. Internal DNS name for the pod will be used if CommonName is## not provided. DNS name format is *.minio.default.svc.cluster.localcertConfig: { }## PodManagement policy for MinIO Tenant Pods. Can be "OrderedReady" or "Parallel"## Refer https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#pod-management-policy## for details.podManagementPolicy: Parallel## Secret with credentials and configurations to be used by MinIO Tenant.configuration:
name: ven-minio-cfg## Add environment variables to be set in MinIO container (https://github.com/minio/minio/tree/master/docs/config)env:
- name: MINIO_BROWSER_REDIRECT_URLvalue: "https://minio-console.my-domain.io"# - name: MINIO_SERVER_URL# value: https://minio.my-domain.io
- name: MINIO_BROWSERvalue: on# - name: MINIO_ROOT_USER# value: minio# - name: MINIO_ROOT_PASSWORD# value: minio123## serviceMetadata allows passing additional labels and annotations to MinIO and Console specific## services created by the operator.serviceMetadata:
minioServiceLabels: { }minioServiceAnnotations: { }consoleServiceLabels: { }consoleServiceAnnotations: { }## PriorityClassName indicates the Pod priority and hence importance of a Pod relative to other Pods.## This is applied to MinIO pods only.## Refer Kubernetes documentation for details https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass/priorityClassName: ""## Use this field to provide one or more external CA certificates. This is used by MinIO## to verify TLS connections with other applications.## Certificate secret files will be mounted under /tmp/certs/CAs folder, supported types:## Opaque | kubernetes.io/tls | cert-manager.io/v1alpha2 | cert-manager.io/v1#### ie:#### externalCaCertSecret:## - name: ca-certificate-1## type: Opaque## - name: ca-certificate-2## type: Opaque## - name: ca-certificate-3## type: Opaque#### Create secrets as explained here:## https://github.com/minio/minio/tree/master/docs/tls/kubernetes#2-create-kubernetes-secretexternalCaCertSecret: [ ]## Use this field to provide one or more Secrets with external certificates. This can be used to configure## TLS for MinIO Tenant pods.## Certificate secret files will be mounted under /tmp/certs folder, supported types:## Opaque | kubernetes.io/tls | cert-manager.io/v1alpha2 | cert-manager.io/v1#### ie:#### externalCertSecret:## - name: domain-certificate-1## type: kubernetes.io/tls## - name: domain-certificate-2## type: kubernetes.io/tls## - name:domain-certificate-3## type: kubernetes.io/tls#### Create secrets as explained here:## https://github.com/minio/minio/tree/master/docs/tls/kubernetes#2-create-kubernetes-secretexternalCertSecret: [ ]## Use this field to provide client certificates for MinIO & KES. This can be used to configure## mTLS for MinIO and your KES server. Files will be mounted under /tmp/certs folder, supported types:## Opaque | kubernetes.io/tls | cert-manager.io/v1alpha2 | cert-manager.io/v1## ie:#### externalClientCertSecret:## name: mtls-certificates-for-tenant## type: Opaque#### Create secrets as explained here:## https://github.com/minio/minio/tree/master/docs/tls/kubernetes#2-create-kubernetes-secret# externalClientCertSecret: {}#### Use this field to provide additional client certificate for the MinIO Tenant## Certificate secret files will be mounted under /tmp/certs folder, supported types:## Opaque | kubernetes.io/tls | cert-manager.io/v1alpha2 | cert-manager.io/v1#### mount path inside container:#### certs## |## + client-0## | + client.crt## | + client.key## + client-1## | + client.crt## | + client.key## + client-2## | + client.crt## | + client.key## ie:#### externalClientCertSecrets:## - name: client-certificate-1## type: kubernetes.io/tls## - name: client-certificate-2## type: kubernetes.io/tls## - name:client-certificate-3## type: kubernetes.io/tls#### Create secrets as explained here:## https://github.com/minio/minio/tree/master/docs/tls/kubernetes#2-create-kubernetes-secretexternalClientCertSecrets: [ ]## Registry location and Tag to download MinIO Server imageimage: quay.io/minio/minio:RELEASE.2023-11-15T20-43-25Z# image: quay.io/minio/minio:RELEASE.2023-05-04T21-44-30ZimagePullSecret: { }## Mount path where PV will be mounted inside container(s).mountPath: /export## Sub path inside Mount path where MinIO stores data.## WARNING:## We recommend you to keep the same mountPath and the same subPath once the## Tenant has been deployed over your different PVs.## This is because if you change these values once Tenant is deployed, then## you will end up with multiple paths for different buckets. So please, be## very careful to keep same value for the life of the Tenant.subPath: ""## Service account to be used for all the MinIO PodsserviceAccountName: ""## Specification for MinIO Pool(s) in this Tenant.pools:
## Servers specifies the number of MinIO Tenant Pods / Servers in this pool.## For standalone mode, supply 1. For distributed mode, supply 4 or more.## Note that the operator does not support upgrading from standalone to distributed mode.
- servers: 2## custom name for the poolname: pool-0## Specify one or more Pod Topology Spread Constraints to apply to pods deployed in the MinIO pool.## https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraintstopologySpreadConstraints: [ ]## volumesPerServer specifies the number of volumes attached per MinIO Tenant Pod / Server.volumesPerServer: 2## nodeSelector parameters for MinIO Pods. It specifies a map of key-value pairs. For the pod to be## eligible to run on a node, the node must have each of the## indicated key-value pairs as labels.## Read more here: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/nodeSelector: { }## Used to specify a toleration for a podtolerations: [ ]## Affinity settings for MinIO pods. Read more about affinity## here: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity.affinity:
nodeAffinity: { }podAffinity: { }podAntiAffinity: { }## Configure resource requests and limits for MinIO containersresources: { }## This VolumeClaimTemplate is used across all the volumes provisioned for MinIO Tenant in this## Pool.volumeClaimTemplate:
apiVersion: v1kind: persistentvolumeclaimsmetadata: { }spec:
accessModes:
- ReadWriteOnceresources:
requests:
storage: 20GistorageClassName: hcloud-volumesstatus: { }## Configure Pod's security context## We recommend to skip the recursive permission change by using## fsGroupChangePolicy as OnRootMismatch because it can be pretty## expensive for larger volumes with lots of small files.securityContext:
runAsUser: 1000runAsGroup: 1000runAsNonRoot: truefsGroup: 1000fsGroupChangePolicy: "OnRootMismatch"## Configure container security contextcontainerSecurityContext:
runAsUser: 1000runAsGroup: 1000runAsNonRoot: true## Enable automatic Kubernetes based certificate generation and signing as explained in## https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-clusterrequestAutoCert: true## Prometheus setup for MinIO Tenant.# prometheus:# image: "" # defaults to quay.io/prometheus/prometheus:latest# env: [ ]# sidecarimage: "" # defaults to alpine# initimage: "" # defaults to busybox:1.33.1# diskCapacityGB: 1# storageClassName: standard# annotations: { }# labels: { }# nodeSelector: { }# affinity:# nodeAffinity: { }# podAffinity: { }# podAntiAffinity: { }# resources: { }# serviceAccountName: ""# securityContext:# runAsUser: 1000# runAsGroup: 1000# runAsNonRoot: true# fsGroup: 1000## Prometheus Operator's Service Monitor for MinIO Tenant Pods.# prometheusOperator:# labels:# app: minio-sm## Audit Logs will be deprecated soon, commenting out for now!.## LogSearch API setup for MinIO Tenant.# log:# image: "" # defaults to minio/operator:v5.0.11# env: [ ]# resources: { }# nodeSelector: { }# affinity:# nodeAffinity: { }# podAffinity: { }# podAntiAffinity: { }# tolerations: [ ]# annotations: { }# labels: { }# audit:# diskCapacityGB: 1# ## Postgres setup for LogSearch API# db:# image: "" # defaults to library/postgres# env: [ ]# initimage: "" # defaults to busybox:1.33.1# volumeClaimTemplate:# metadata: { }# spec:# storageClassName: standard# accessModes:# - ReadWriteOnce# resources:# requests:# storage: 1Gi# resources: { }# nodeSelector: { }# affinity:# nodeAffinity: { }# podAffinity: { }# podAntiAffinity: { }# tolerations: [ ]# annotations: { }# labels: { }# serviceAccountName: ""# securityContext:# runAsUser: 999# runAsGroup: 999# runAsNonRoot: true# fsGroup: 999# serviceAccountName: ""# securityContext:# runAsUser: 1000# runAsGroup: 1000# runAsNonRoot: true# fsGroup: 1000
The text was updated successfully, but these errors were encountered:
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce (for bugs)
https://minio.my-sys.svc.cluster.local/hello/world/Screenshot%202023-11-21%20at%2004.17.06.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=2FAHQ8000OLBM2QU6DO2%2F20231124%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231124T062642Z&X-Amz-Expires=604800&X-Amz-Security-Token=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiIyRkFIUTgwMDBPTEJNMlFVNkRPMiIsImV4cCI6MTcwMDg1MDA5MSwicGFyZW50IjoiY29uc29sZSJ9.4KzSELvaSRvQXO1mmOXpKzHFgeutK50DVuuisvC2SclnESq5FNkKyFyd9hmBgGQlIOzgBOLf5btWLjYiynmwyA&X-Amz-SignedHeaders=host&versionId=6ff09fa2-d5e2-4b95-b734-30d29c9df764&X-Amz-Signature=8e059c7f6e4109bc235cd9ce2b9e7268f1f4552cd3eaba4f102d1633b7f79acc
but should look like thishttps://minio-console.my-domain.io ...
Context
Regression
Your Environment
minio-operator
): v5.0.11uname -a
): ubuntu 22.04helm
helm: secret artifact
helm: applied cfg secret
helm: chart overwrite.yaml
helm: template output
kustomize
kustomize applied tenant 1 pod
cluster config kustomize
The text was updated successfully, but these errors were encountered: