-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
multicluster configuration steps to make NodePort gateway work #6983
Comments
@redblade thanks for taking the time to submit this and I apologize for taking so long to update this issue. I'll run through the steps you outlined and let you know what I find. |
@redblade can you tell me more about the clusters? Are they running in a cloud provider, or are you running them locally with something like kind? |
Hi, they are two on-premise clusters running on OpenStack, where LoadBalancer service is not available, this is why I am interested in the new NodePort feature. There are no firewalls or network policies blocking any traffic, the security on the ports is disabled and there is full connectivity among the two clusters. |
thanks @redblade that helps to understand the networking between the clusters. I think I can try to reproduce this with local k3d or kind clusters |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
any update on this one ? |
follow up of 6059
I am testing Linkerd multicluster with NodePort using Linkerd edge-21.8.4 release with two Kubernetes 1.22.1 "west" and "east"
west/east config
west: master IP 192.168.111.15, worker IP 192.168.111.14, Pod CIDR 11.1.0.0/16
east: master IP 192.168.111.6, worker IP 192.168.111.10, Pod CIDR 12.1.0.0/16
certificates
linkerd install:
viz install:
multicluster install with NodePort
Ports are 30500 and 30501 (west), 31500 and 31501 (east)
multicluster link setup (created a link on west, referencing east IP/ports)
I am using the east gateway IP of the master (192.168.111.6) and the ports (31500, 31501)
multicluster verify
multicluster check
Bug Report
For the tests, I am using https://linkerd.io/2.10/tasks/multicluster/#installing-the-test-services.
Services are deployed correctly but remote invocation fails (curl does not get any answer from the remote service, see below)
Basically, west does not connect to east. No logs in the linkerd-service-mirror-east/service-mirror Pod
I have also tried to create an nginx deployment, exposed as svc in a test3 ns, same issue
the logs in the linkerd-service-mirror-east-ffd4448fb-52hxz -n linkerd-multicluster service-mirror seems fine
the service mirror is correctly in test3 ns on west but it is not responding
"HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.)"
Am I missing something in the configuration for NodePort multicluster reported above?
The text was updated successfully, but these errors were encountered: