← 输入框|github.com|刷新
Skip to content

Minio won't work on clusters with custom clusterDomain #2895

Closed

Description

@Givemeurcookies

🐞 Bug report

Describe the bug

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:

value: "{{ .Release.Name }}-minio.{{ .Release.Namespace }}.svc.cluster.local"

Steps To Reproduce

  1. Set up cluster with clusterDomain
  2. Minio won't work

Expected behavior

Allow setting clusterDomain in Helm chart values

Activity

  1. J12934 commented on Feb 8, 2025

    @J12934
    Member

    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.

  2. moved this from Triage to Backlog in secureCodeBoxon Feb 8, 2025
  3. added a commit that references this issue on Feb 24, 2025
  4. caffeine-rohit commented on Feb 25, 2025

    @caffeine-rohit

    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! 🚀

  5. added a commit that references this issue on Jun 27, 2026
    030acbb
  6. moved this from Backlog to Done in secureCodeBoxon Jun 29, 2026
  7. added a commit that references this issue on Jun 29, 2026
    67d6714
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugBugshelp wantedExtra attention is needed

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions