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
{{ message }}
Repository navigation
Minio won't work on clusters with custom clusterDomain #2895
Some clusters might have a custom cluster domain, in the manager helm chart the cluster domain is hardcoded so there's no way to override the value defined at:
Thanks for the report.
Never customized that, based on your experience, if you modify the clustername does that then also set the dns search path for the containers correctly?
Meaning that we could just drop the cluster.local and it would work for everybody without modification.
Meaning that we could just drop the cluster.local and it would work for everybody without modification.
Hey @J12934 , Referring to this PR
We analyzed the difference between removing .svc.cluster.local and making the clusterDomain configurable. Here’s why our approach is more robust:
1️⃣ Flexibility & Customization: Our method allows users to configure clusterDomain dynamically, ensuring compatibility with custom Kubernetes environments (e.g., multi-cluster setups or corporate DNS configurations). Simply removing .svc.cluster.local assumes all clusters follow the default DNS resolution, which may not always be the case.
2️⃣ Backward Compatibility: Many Kubernetes deployments rely on the explicit .svc.cluster.localstructure. Removing it could break existing setups that depend on a fully qualified domain name (FQDN). Our approach keeps the default behavior intact while allowing users to override it if needed.
3️⃣ Best Practices & Industry Standards: Other Helm charts for similar services (e.g., external storage providers) offer clusterDomain as a configurable parameter to support varied networking environments. This approach aligns SecureCodeBox with industry best practices.
That said, if the team strongly prefers removing .svc.cluster.local , we’re happy to test that as well. Let us know how you'd like to proceed! 🚀
Activity
J12934 commentedon Feb 8, 2025
Hi @Givemeurcookies
Thanks for the report.
Never customized that, based on your experience, if you modify the clustername does that then also set the dns search path for the containers correctly?
Meaning that we could just drop the cluster.local and it would work for everybody without modification.
Closes Issue secureCodeBox#2895
caffeine-rohit commentedon Feb 25, 2025
Hey @J12934 , Referring to this PR
We analyzed the difference between removing
.svc.cluster.localand making theclusterDomainconfigurable. Here’s why our approach is more robust:1️⃣ Flexibility & Customization: Our method allows users to configure
clusterDomaindynamically, ensuring compatibility with custom Kubernetes environments (e.g., multi-cluster setups or corporate DNS configurations). Simply removing.svc.cluster.localassumes all clusters follow the default DNS resolution, which may not always be the case.2️⃣ Backward Compatibility: Many Kubernetes deployments rely on the explicit
.svc.cluster.localstructure. Removing it could break existing setups that depend on a fully qualified domain name (FQDN). Our approach keeps the default behavior intact while allowing users to override it if needed.3️⃣ Best Practices & Industry Standards: Other Helm charts for similar services (e.g., external storage providers) offer
clusterDomainas a configurable parameter to support varied networking environments. This approach aligns SecureCodeBox with industry best practices.That said, if the team strongly prefers removing
.svc.cluster.local, we’re happy to test that as well. Let us know how you'd like to proceed! 🚀operator: make minio endpoint cluster domain configurable
operator: make minio endpoint cluster domain configurable