[k8s-5.0.1]: In multi cluster nested environment, Pod with same name and namespace name is not reachable
Bug #1781119 reported by
Pulkit Tandon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Fix Committed
|
High
|
Yuvaraja Mariappan | |||
Trunk |
Fix Committed
|
High
|
Yuvaraja Mariappan |
Bug Description
R5.0.1. Build 122
Multi cluster Nested k8s provisioning.
Created Pod with name "busybox" in namespace "test" in cluster 1.
Cluster 1 Pod Subnet = 10.36.0.0/12
This Pod is reachable from any Pod within the same cluster
Created Pod with name "busybox" in namespace "test" in cluster 2.
Cluster 2 Pod Subnet = 10.52.0.0/12
This Pod is not reachable via any Pod within the cluster.
Verified that any other Pod created does not have any reachability issue until the namespace and pod names are same.
summary: |
- [k8s-5.0.1]: In multi cluster nested environment, 2nd cluster doesn't - get the service IP for default kubernetes service + [k8s-5.0.1]: In multi cluster nested environment, Pod with same name and + namespace name is not reachable |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/44712
Submitter: Yuvaraja Mariappan