-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Comments
/kind feature |
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). |
Feature Description
How does it work
Svc DNS
Firstly create
FederatedDeployment
andFederatedService
objects(user can do that by creating a workload on ks console)Secondly create
Domain
(eg: foo.bar.com) andServiceDNSRecord
objects(the name of the svc and domain name)Thirdly a
DNSEndpoint
object(hostname and ip relationships) will be created by the DNS Endpoint ControllerFinally ExternalDNS will update the dns record to the etcd and coredns will update itself from etcd
Ingress DNS
Firstly create
FederatedDeployment
andFederatedService
andFederatedIngress
objects(user can do that by creating a workload svc on ks console)Secondly create
IngressDNSRecord
objectThirdly a
DNSEndpoint
object will be created by the DNS Endpoint ControllerFinally ExternalDNS will update the dns record to the etcd and coredns will update itself from etcd
Limitations
Potential risk
The text was updated successfully, but these errors were encountered: