xness
Dabbler
- Joined
- Jun 3, 2022
- Messages
- 30
When running MinIO in regular mode (aka not distributed, but probably the same there) via Kubernetes/BTCharts and setting hostname of MinIO to hyper.s3.domain.tld in the GUI wizard, login via the MinIO web interface fails with the error message "Failed to dial up 10.10.10.10:9000"
It resolves the hostname (hyper.s3.domain.tld) properly to the IPv4 (10.10.10.10) set on DNS server, but is unable to access its own parent network interface's IPv4 address and doesn't realize it is 10.10.10.10 itself.
I am currently working around this by adding 127.0.0.1 hyper.s3.domain.tld to /etc/hosts of the Docker container, but it's obviously removed whenever I restart. Couldn't find any way to add the hostname as an alias for the pod on Kubernetes level – any ideas on how to solve this?
It resolves the hostname (hyper.s3.domain.tld) properly to the IPv4 (10.10.10.10) set on DNS server, but is unable to access its own parent network interface's IPv4 address and doesn't realize it is 10.10.10.10 itself.
I am currently working around this by adding 127.0.0.1 hyper.s3.domain.tld to /etc/hosts of the Docker container, but it's obviously removed whenever I restart. Couldn't find any way to add the hostname as an alias for the pod on Kubernetes level – any ideas on how to solve this?
