[kubic-bugs] [Bug 1135973] New: Change Description of "Admin Node" in the installer Build 20190520
http://bugzilla.suse.com/show_bug.cgi?id=1135973 Bug ID: 1135973 Summary: Change Description of "Admin Node" in the installer Build 20190520 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs@opensuse.org Reporter: jason.evans@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Issue: The current description does not say that this is a Kubernetes Master Node. This isn't obvious from the description that this is what it is. Note: Is there a reason for calling this an "Admin node" and not a "Master node"? Those familiar with CaaSP 1-3 may associate this with Velum incorrectly. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135973 Jason Evans <jason.evans@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason.evans@suse.com Found By|--- |Community User -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135973 http://bugzilla.suse.com/show_bug.cgi?id=1135973#c1 --- Comment #1 from Thorsten Kukuk <kukuk@suse.com> --- I discussed already with rbrown that we need a better description, as I was afraid that people will get this mixed up with velum. The "Admin Node" role is the node running "KubicD". Today we can say, that the "master node" and "admin node" are identical. But if you think about multi-master configurations (currently experimental in kubeadm), then an admin node is always a master node, but a master node does not need to be necessarily an admin node. So I don't like "Master Node", because then users would install every master node with this system role, and we would have e.g. three salt master and three kubicd, but none of them works together. What we need to make clear to the user: - We need exactly one admin node (which will also be a master node) - All other machines have to be installed with the second system role (currently worker node), and with kubicctl you will define which ones will become additional kubernetes master and which ones worker. Similar to velum. I'm happy about every better suggestion. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1135973 http://bugzilla.suse.com/show_bug.cgi?id=1135973#c2 --- Comment #2 from Jason Evans <jason.evans@suse.com> --- My suggestion is that we should just be explicit as to what the admin node is. The first bullet under Kubic Worker Node is: MicroOS-based kubernetes Worker Nodes The first bullet under Kubic Admin Node should be: First MicroOS-based kubernetes Master Node In documentation, we can describe how to add more masters once we are comfortable adding them with kubeadm -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠novell.com