-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.15.0
-
No
-
2
-
OSDOCS Sprint 249
-
1
-
False
-
-
-
Release Note Not Required
-
In Progress
Description of problem:
From 4.14 to 4.15, the ovnkube-control-plane deployment has scaled back from 3 pods to 2. The networking guide in 4.14 has many references to this pod and shows 3 pods in all the examples. That was correct for 4.14 but it should be 2 in 4.15. Also, this paragraph needs to be changed: "The Kubernetes control plane nodes each contain an ovnkube-control-plane pod which does the central IP address management (IPAM) allocation for each node in the cluster. At any given time a single ovnkube-control-plane pod is the leader." Should say: "The Kubernetes control plane nodes contain two ovnkube-control-plane pods, on separate nodes, which does the central IP address management (IPAM) allocation for each node in the cluster. At any given time a single ovnkube-control-plane pod is the leader."
Version-Release number of selected component (if applicable):
4.15+
How reproducible:
100%
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: