In version: v1.20, the kubernetes do enhancement for SVC:
Add dual-stack Services (alpha). This is a BREAKING CHANGE to an alpha API. It changes the dual-stack API wrt Service from a single ipFamily field to 3 fields: ipFamilyPolicy (SingleStack, PreferDualStack, RequireDualStack), ipFamilies (a list of families assigned), and clusterIPs (inclusive of clusterIP). Most users do not need to set anything at all, defaulting will handle it for them. Services are single-stack unless the user asks for dual-stack. This is all gated by the "IPv6DualStack" feature gate. (#91824, @khenidak) [SIG API Machinery, Apps, CLI, Network, Node, Scheduling and Testing]
Basically, in latest version of kubernetes, if you create a SVC without define the ClusterIPs, the kubernetes will generate it automatic based on ClusterIP, like this:
What steps did you take and what happened: There are tons of warning in log of
syncer
, said:The problem is related to the kubernetes version, The tenant cluster version is:
and the version in super cluster is:
In version: v1.20, the kubernetes do enhancement for SVC:
Basically, in latest version of kubernetes, if you create a
SVC
without define theClusterIPs
, the kubernetes will generate it automatic based onClusterIP
, like this:It will make
svc
in super cluster and tenant cluster always different.Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]