Second master node installed with unsupported method

Bug #1846829 reported by Bart Wensley on 2019-10-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
David Sullivan

Bug Description

Brief Description
When we originally implemented the deployment of the kubernetes HA cluster using kubeadm, the instructions for the second master node were to copy certificate files from the first master node and then run the "kubeadm init" command with the same yaml file used on the first master node. However, in a subsequent release, the instructions (see changed to use the "kubeadm join" with a --control-plane option instead. This approach is simpler and the approach we are currently using is no longer supported (although it still seems to be working).

Minor - although I expect the method we are using will no longer work at some point

Steps to Reproduce
Install a system with two controllers

Expected Behavior
We should be using the supported kubadm instructions.

Actual Behavior
We are following obsolete instructions.


System Configuration
Any system with two controller hosts

Branch/Pull Time/Commit

Last Pass


Test Activity
Developer Testing

Ghada Khalil (gkhalil) wrote :

Marking as stx.3.0 / medium priority - prefer to align on the supported method for the stx.3.0 release.

tags: added: stx.containers
tags: added: stx.3.0
Changed in starlingx:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Bart Wensley (bartwensley)
Changed in starlingx:
assignee: Bart Wensley (bartwensley) → David Sullivan (dsullivanwr)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers