Kubernetes cluster is getting IPs from “Management Network” instead of "Cluster Host Network"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Fabiano Correa Mercer |
Bug Description
Brief Description
-----------------
According to the StarlingX documentation (https:/
But Nodes are using IPs from management network.
Severity
--------
Minor
Steps to Reproduce
------------------
configure an AIO-DX or controlers+worker scenario:
( https:/
Defines the IPs of “Cluster-host subnet” and “Management subnet” respectively.
Included the same IPs in the Localhost.yml file
Bootstrap the Ansible-playbook using the Localhost.yml file
Check output of commands:
kubectl get nodes -A -o wide
kubectl get pod -A -o wide
Expected Behavior
------------------
Kubectl nodes should use IPs from Cluster-host subnet.
Check output of commands:
kubectl get nodes -A -o wide
kubectl get pod -A -o wide
Actual Behavior
----------------
After completion of Duplex installation Bootstrapping, it was analyzed that Controller-0 and Controller-1 were got IP from “management subnet” instead “Cluster-host subnet”
Check output of commands:
kubectl get nodes -A -o wide
kubectl get pod -A -o wide
Reproducibility
---------------
100% reproducible
System Configuration
-------
Two node system, Multi-node system
IPv4,IPv6
Branch/Pull Time/Commit
-------
Probably introduced by:
https:/
Last Pass
---------
N/A
Timestamp/Logs
--------------
[root@controller-0 sysadmin(
+-----
| name | network |
+-----
| cluster-host-subnet | fd02:: |
| management | fd01:: |
+-----
[sysadmin@
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP
compute-0 Ready <none> 14h v1.24.4 fd01::7fe6:
controller-0 Ready control-
controller-1 Ready control-
[sysadmin@
kube-system calico-node-6v4gg 1/1 Running fd01::3 controller-1
kube-system calico-node-r5qhr 1/1 Running fd01::2 controller-0
kube-system cephfs-
kube-system cephfs-
Test Activity
-------------
Evaluation
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Fabiano Correa Mercer (fcorream) |
Changed in starlingx: | |
status: | New → In Progress |
tags: | added: stx.networking |
tags: | added: stx.8.0 |
Reviewed: https:/ /review. opendev. org/c/starlingx /config/ +/867737 /opendev. org/starlingx/ config/ commit/ 891e71e2f2d59bd 82c66ca7551534a 2b9f300449
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 891e71e2f2d59bd 82c66ca7551534a 2b9f300449
Author: Fabiano Mercer <email address hidden>
Date: Wed Dec 14 16:24:01 2022 -0300
Attach all nodes to the cluster host network
Problem: Nodes in the cluster are attached to the management
network instead of the cluster host network.
According to StarlingX documentation, all nodes in the cluster
must be attached to the cluster host network.
Test plan ( Debian only )
(2controllers , 1 worker)
(2controllers , 1 worker)
PASS Installed 2+1 system using IPv4
PASS Installed 2+1 system using IPv6
PASS AIO-SX system using IPv4
PASS AIO-SX system using IPv6
PASS AIO-SX system external access to a Kubernetes service
PASS AIO-DX system using IPv4 and tested traffic between PODs
PASS AIO-DX system using IPv6 and tested traffic between PODs
PASS AIO-SX upgrade
PASS STANDARD ( 2 controllers + 1 worker ) upgrade
PASS STANDARD ( 2 controllers + 1 worker ) pod -> external traffic
Closes-Bug: #1999690
Signed-off-by: Fabiano Mercer <email address hidden> a6fe193aab5cb69 2d3baf76c4b
Change-Id: Ib9ea1a857f657c