Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Support muti cluster service dns and ingress dns #3009

Open
swiftslee opened this issue Oct 10, 2020 · 6 comments
Open

Feature: Support muti cluster service dns and ingress dns #3009

swiftslee opened this issue Oct 10, 2020 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@swiftslee
Copy link
Contributor

swiftslee commented Oct 10, 2020

Feature Description

  • Create an Ingress object once and can visit the same ingress host(highly available) in any cluster
  • Create a loadbalancer svc object once and can visit the same svc name host(highly available) in any cluster

How does it work

Svc DNS

  • Firstly create FederatedDeployment and FederatedService objects(user can do that by creating a workload on ks console)

  • Secondly create Domain(eg: foo.bar.com) and ServiceDNSRecord objects(the name of the svc and domain name)

  • Thirdly a DNSEndpoint object(hostname and ip relationships) will be created by the DNS Endpoint Controller

  • Finally ExternalDNS will update the dns record to the etcd and coredns will update itself from etcd

Ingress DNS

  • Firstly create FederatedDeployment and FederatedService and FederatedIngress objects(user can do that by creating a workload svc on ks console)

  • Secondly create IngressDNSRecord object

  • Thirdly a DNSEndpoint object will be created by the DNS Endpoint Controller

  • Finally ExternalDNS will update the dns record to the etcd and coredns will update itself from etcd

Limitations

  • The type of svc must be LoadBalancer
  • Extra etcd cluster to store data
  • Individual dns server such as coredns or other public cloud provider
  • Extra external-dns pod in host cluster
  • Nodes must have region and zone lables

Potential risk

  • The kubefed community is discussing remove FederatedIngress& CrossClusterDiscovery feature #284 pull
@swiftslee
Copy link
Contributor Author

swiftslee commented Oct 10, 2020

/kind feature

@ks-ci-bot ks-ci-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 10, 2020
@swiftslee
Copy link
Contributor Author

swiftslee commented Nov 2, 2020

Kubefed community has disabled those two features by default and will remove them in the feature.

@swiftslee swiftslee reopened this Nov 2, 2020
@luoMonkeyKing
Copy link

Kubefed community has disabled those two features by default and will remove them in the feature.

Hello, I found that these two functions have been deleted in the v.7.0 version. Is there any other way to achieve the same function? I also did not find any relevant operation cases in the new version of kubefed documentation.

@swiftslee
Copy link
Contributor Author

Kubefed community has disabled those two features by default and will remove them in the feature.

Hello, I found that these two functions have been deleted in the v.7.0 version. Is there any other way to achieve the same function? I also did not find any relevant operation cases in the new version of kubefed documentation.

Hey brother. If you are interested in this feature, we can have a talk on slack. https://kubesphere.slack.com/archives/CBJ1A2UCB

@luoMonkeyKing
Copy link

luoMonkeyKing commented Apr 20, 2021

Kubefed community has disabled those two features by default and will remove them in the feature.

Hello, I found that these two functions have been deleted in the v.7.0 version. Is there any other way to achieve the same function? I also did not find any relevant operation cases in the new version of kubefed documentation.

Hey brother. If you are interested in this feature, we can have a talk on slack. https://kubesphere.slack.com/archives/CBJ1A2UCB

Okay, but I can’t log in to the link you sent. Do I need to add my email to the workspace? My mailbox [email protected]

@FeynmanZhou
Copy link
Member

Kubefed community has disabled those two features by default and will remove them in the feature.

Hello, I found that these two functions have been deleted in the v.7.0 version. Is there any other way to achieve the same function? I also did not find any relevant operation cases in the new version of kubefed documentation.

Hey brother. If you are interested in this feature, we can have a talk on slack. https://kubesphere.slack.com/archives/CBJ1A2UCB

Okay, but I can’t log in to the link you sent. Do I need to add my email to the workspace? My mailbox [email protected]

@luoMonkeyKing You can try this link, or join the KubeSphere community on the WeChat group (The entry is on https://kubesphere.io).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants