Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-58537

Use DNS for cluster peers - K8s support

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Data Center - Core
    • None
    • 3
    • 2
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Hi,

      I am currently trying to run confluence data center nodes on Kubernetes.
      Since the underlaying network layer does not support multicast, I am stuck with tcp_ip cluster.type.
      As pods get assigned new IP-addresses on rebuild and I need to rebuild the pods in order to change the configuration, there seems to be a circular dependency I cannot get over.

      As I see many people struggling with this exact part on K8s, I'd like to suggest the property of cluster.peers to be DNS names, a bit like CONFSERVER-53527, but without the synchrony-part.

      The config-property would be extended like this:

      <property name="confluence.cluster.peers">192.168.1.1,"confluence-0.confluence.cluster.local"</property> <!-- A comma-separated list of node IP addresses, without spaces -->

      The naive behavior-changes of the cluster-node discovery would consist of a simpe DNS-query while parsing the config, then recheck the DNS every time a node fails.

      This change would directly enable Confluence to be run on Kubernetes.

       

              Unassigned Unassigned
              k.sisterhenn Kai Sisterhenn
              Votes:
              8 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: