Hello everyone,
I’m using Kong API Gateway to config MiniO.
Now, I can access to MiniO portal (port 9001) with Kong.
Unfortunately, I can’t use Minio API (port 9000) with Kong.
Anyone use Kong for MiniO like me, please help me config!
Thank you!
Hi
If you intend using MinIO with a subpath, I read on stackoverflow that is not possible to achive, maybe without subpath.
I’m struggling to configure Kong to use properly MinIO with a subpath, did you achive that? in case… how?
i am too facing the same issue when using subpath,
is it possible configure MiniO behind kong ingress via subpath, please help!
I am trying to set the minio behind the kong ingress controller with https enabled. Here the TLS communication will be terminated in kong
The routing url which I have set /storage
I have set the below values in values.yaml
Variables:
- env:
- name: MINIO_LOG_LEVEL
value: DEBUG
- name: MINO_SERVER_URL
value: https://domain:30007/storage
- name: MINIO_BROWSER_REDIRECT_URL
value: https://domain:30007/storage
minio-ingress.yaml:
` apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: minio-ingress
labels:
app.kubernetes.io/instance: kong
app.kubernetes.io/managed-by: Helm
annotations:
konghq.com/strip-path: "true"
kubernetes.io/ingress.class: "kong"
spec:
ingressClassName: kong
tls:
- hosts:
- fresh.com
secretName: kong
rules:
- host: fresh.com
http:
paths:
- path: /storage
pathType: Prefix
backend:
service:
name: minio-test
port:
number: 9001`
When we login into console and check the presigned url for a file, its still pointing to [http//localhost:9000/test/22.log] which should be https://domain:30007/storage/test/22.log.
