[k8s]: k8s master HA not supported
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
New
|
High
|
Michael Henkel | |||
Trunk |
New
|
High
|
Michael Henkel |
Bug Description
R5.0-ocata-50.
Tried ansible provisioning with following roles:
bms1:
provider: bms
ip: 77.77.1.20
roles:
config_
config:
control:
analytics
analytics:
webui:
k8s_master:
kubemanager:
bms2:
provider: bms
ip: 77.77.1.30
roles:
config_
config:
control:
analytics
analytics:
webui:
k8s_master:
kubemanager:
bms3:
provider: bms
ip: 77.77.1.11
roles:
config_
config:
control:
analytics
analytics:
webui:
k8s_master:
kubemanager:
bms4:
provider: bms
ip: 77.77.1.21
roles:
k8s_node:
vrouter:
bms5:
provider: bms
ip: 77.77.1.31
roles:
k8s_node:
vrouter:
K8s master got installed on only 1 node.
k8s master HA provisioning is not supported yet.
Need to enhance the ansible-deployer to support that.
NOTE: K8s master HA is often confused with kube-manager HA. Please note that k8s-master HA does not have anything to do with contrail and is a feature supported by k8s.
tags: | added: releasenote |
K8S HA implementation is not trivial as it requires vrrp and haproxy. The need for vrrp makes it imposible to deploy the masters across different subnets.