Open sangeethah opened 5 years ago
It looks like a problem with upstream external dns, i reproduced the problem with external dns deployment only, and i opened an issue with the upstream project https://github.com/kubernetes-incubator/external-dns/issues/887
Moving out 2.2 release milestone as the issue seems to be an upstream one
@alena1108 This has been fixed upstream. We should be able to pull in the fix by upgrading to the latest release of external-dns. https://github.com/kubernetes-incubator/external-dns/pull/1034
Can this issue be looked at since it has been fixed in the upstream repo? I'm getting this issue on all of my clusters in the production
Rancher server version - Build from master (1/28)
HA Set up with following clusters: Cluster1 - 1 node (all roles) Cluster2 - 1 node (all roles)
Steps to reproduce the problem:
Ingress that gets created in
cattle-global-data
namespace has node ips from cluster1 and cluster2 as expected.In cloudflare console , A record for "test1.test.com" points only to 1 ip address.