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

The cluster failed to establish a connection #3265

Open
xuchuan-666 opened this issue Jan 14, 2025 · 3 comments
Open

The cluster failed to establish a connection #3265

xuchuan-666 opened this issue Jan 14, 2025 · 3 comments
Assignees
Labels
bug Something isn't working need-info

Comments

@xuchuan-666
Copy link

What happened:
all components of cluster1 and cluster2 are correct and logs are normal, and no errors are reported. However, the two clusters are not connected. For example, diagnose all of them by subctl and some of them are not ready, but I created them according to requirements

What you expected to happen:
The cluster can create connections

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Diagnose information (use subctl diagnose all):
  • [root@yonsuite-test-172-20-30-245 ~]# subctl diagnose all
    Cluster "kubernetes"
    ✓ Checking Submariner support for the Kubernetes version
    ✓ Kubernetes version "v1.32.0" is supported

✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
✓ Checking DaemonSet "submariner-gateway"
✓ Checking DaemonSet "submariner-routeagent"
✓ Checking DaemonSet "submariner-metrics-proxy"
✓ Checking Deployment "submariner-lighthouse-agent"
✓ Checking Deployment "submariner-lighthouse-coredns"
✓ Checking the status of all Submariner pods
✓ Checking that gateway metrics are accessible from non-gateway nodes

✓ Checking Submariner support for the CNI network plugin
✓ The detected CNI network plugin ("calico") is supported
✗ Calico CNI detected, checking if the Submariner IPPool pre-requisites are configured
✗ Error obtaining IPPools: the server could not find the requested resource
✗ Checking gateway connections
✗ There are no active connections on gateway "yonsuite-test-172-20-30-75"
✓ Checking route agent connections
✓ There are no remote endpoint connections on route agent "172.20.30.245"
✓ There are no remote endpoint connections on route agent "172.20.30.75"
✓ Checking Submariner support for the kube-proxy mode
✓ The kube-proxy mode is supported
✗ Checking that firewall configuration allows intra-cluster VXLAN traffic
✗ Unable to obtain a remote endpoint: endpoints.submariner.io "remote Endpoint" not found

✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: devel

  • Gather information (use subctl gather):

  • [root@yonsuite-test-172-20-30-245 ~]# subctl gather
    Cluster "kubernetes"
    Gathering information from cluster "kubernetes"
    ✓ Gathering connectivity logs
    ✓ Found 1 pods matching label selector "app=submariner-gateway"
    ✓ Found 2 pods matching label selector "app=submariner-routeagent"
    ✓ Found 1 pods matching label selector "app=submariner-metrics-proxy"
    ✓ Found 0 pods matching label selector "app=submariner-globalnet"
    ✓ Found 0 pods matching label selector "app=submariner-addon"
    ✓ Gathering connectivity resources
    ✓ Gathering CNI data from 2 pods matching label selector "app=submariner-routeagent"
    ✓ Gathering CNI data from 1 pods matching label selector "app=submariner-gateway"
    ✓ Gathering cable driver data from 1 pods matching label selector "app=submariner-gateway"
    ✓ Found 1 endpoints in namespace "submariner-operator"
    ✓ Found 1 clusters in namespace "submariner-operator"
    ✓ Found 1 gateways in namespace "submariner-operator"
    ✓ Found 2 routeagents in namespace "submariner-operator"
    ✓ Found 0 clusterglobalegressips in namespace ""
    ✓ Found 0 globalegressips in namespace ""
    ✓ Found 0 globalingressips in namespace ""
    ✓ Gathering service-discovery logs
    ✓ Found 3 pods matching label selector "component=submariner-lighthouse"
    ✓ Found 1 pods matching label selector "k8s-app=kube-dns"
    ✓ Gathering service-discovery resources
    ✓ Found 0 serviceexports in namespace ""
    ✓ Found 0 serviceimports in namespace ""
    ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace ""
    ✓ Found 1 configmaps by label selector "component=submariner-lighthouse" in namespace "submariner-operator"
    ✓ Found 1 configmaps by field selector "metadata.name=coredns" in namespace "kube-system"
    ✓ Found 0 services by label selector "submariner.io/exportedServiceRef" in namespace ""
    ✓ Gathering broker logs
    ✓ Gathering broker resources
    ✓ Found 1 endpoints in namespace "submariner-k8s-broker"
    ✓ Found 1 clusters in namespace "submariner-k8s-broker"
    ✓ Found 0 endpointslices by label selector "endpointslice.kubernetes.io/managed-by=lighthouse-agent.submariner.io" in namespace "submariner-k8s-broker"
    ✓ Found 0 serviceimports in namespace "submariner-k8s-broker"
    ✓ Gathering operator logs
    ✓ Found 1 pods matching label selector "name=submariner-operator"
    ✓ Gathering operator resources
    ✓ Found 1 submariners in namespace "submariner-operator"
    ✓ Found 1 servicediscoveries in namespace "submariner-operator"
    ✓ Found 1 deployments by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
    ✓ Found 0 pods by field selector "metadata.name=submariner-operator" in namespace "submariner-operator"
    ✓ Found 1 daemonsets by label selector "app=submariner-gateway" in namespace "submariner-operator"
    ✓ Found 1 pods by label selector "app=submariner-gateway" in namespace "submariner-operator"
    ✓ Found 1 daemonsets by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
    ✓ Found 1 pods by label selector "app=submariner-metrics-proxy" in namespace "submariner-operator"
    ✓ Found 1 daemonsets by label selector "app=submariner-routeagent" in namespace "submariner-operator"
    ✓ Found 2 pods by label selector "app=submariner-routeagent" in namespace "submariner-operator"
    ✓ Found 0 daemonsets by label selector "app=submariner-globalnet" in namespace "submariner-operator"
    ✓ Found 0 pods by label selector "app=submariner-globalnet" in namespace "submariner-operator"
    ✓ Found 1 deployments by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
    ✓ Found 1 pods by label selector "app=submariner-lighthouse-agent" in namespace "submariner-operator"
    ✓ Found 1 deployments by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
    ✓ Found 2 pods by label selector "app=submariner-lighthouse-coredns" in namespace "submariner-operator"
    ✓ Found 0 services by field selector "metadata.name=submariner-gateway" in namespace "submariner-operator"
    Files are stored under directory "submariner-20250114030737/kubernetes"

  • Cloud provider or hardware configuration:
    Local bare metal deployment

  • Install tools:

  • Others:
    [root@yonsuite-test-172-20-30-245 ~]# calicoctl get ippool
    NAME CIDR SELECTOR
    default-ipv4-ippool 192.169.0.0/16 all()
    podwestcluster 192.168.0.0/16 all()
    svcwestcluster 10.96.0.0/16 all()

calico uses vxlan mode and is directly connected to etcd

@xuchuan-666 xuchuan-666 added the bug Something isn't working label Jan 14, 2025
@xuchuan-666
Copy link
Author

@xuchuan-666
Copy link
Author

If you use calico vxlan mode, you must use kubernetes api datasorce, but cannot connect to etcd directly. Otherwise, ippool cannot be discovered. After I modify, I still cannot create a connection

[root@yonsuite-test-172-20-30-245 subctl]# subctl diagnose all
Cluster "kubernetes"
✓ Checking Submariner support for the Kubernetes version
✓ Kubernetes version "v1.32.0" is supported

✓ Non-Globalnet deployment detected - checking that cluster CIDRs do not overlap
✓ Checking DaemonSet "submariner-gateway"
✓ Checking DaemonSet "submariner-routeagent"
✓ Checking DaemonSet "submariner-metrics-proxy"
✓ Checking Deployment "submariner-lighthouse-agent"
✓ Checking Deployment "submariner-lighthouse-coredns"
✓ Checking the status of all Submariner pods
✓ Checking that gateway metrics are accessible from non-gateway nodes

✓ Checking Submariner support for the CNI network plugin
✓ The detected CNI network plugin ("calico") is supported
✓ Calico CNI detected, checking if the Submariner IPPool pre-requisites are configured
✗ Checking gateway connections
✗ There are no active connections on gateway "yonsuite-test-172-20-30-75"
✓ Checking route agent connections
✓ There are no remote endpoint connections on route agent "172.20.30.245"
✓ There are no remote endpoint connections on route agent "172.20.30.75"
✓ Checking Submariner support for the kube-proxy mode
✓ The kube-proxy mode is supported
✗ Checking that firewall configuration allows intra-cluster VXLAN traffic
✗ Unable to obtain a remote endpoint: endpoints.submariner.io "remote Endpoint" not found

✓ Checking that services have been exported properly

Skipping inter-cluster firewall check as it requires two kubeconfigs. Please run "subctl diagnose firewall inter-cluster" command manually.

subctl version: devel

@yboaron
Copy link
Contributor

yboaron commented Jan 20, 2025

Hi @xuchuan-666 ,

From subctl gather I can only see cluster1 endpoint (cluster1-submariner-cable-cluster1-172-20-30-75 ) , can you check GW pod logs in cluster2 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working need-info
Projects
Status: Backlog
Development

No branches or pull requests

2 participants