Verify the remote cluster API Server

Oct 13, 2025 by wbrum.org 97 views

Introduction

In this article, we will explore the issue of establishing a peer connection between OpenShift and MicroShift clusters using liqo. We will delve into the error messages, peering conditions, and relevant log output to identify the root cause of the problem and provide a solution.

Background

Liqo is a Kubernetes project that enables the creation of a multi-cluster environment, allowing for the offloading of workloads between clusters. To establish a peer connection between OpenShift and MicroShift clusters, we need to follow a series of steps, including generating a peer command, authenticating to the remote cluster, and activating outgoing peering.

Error Messages

When attempting to establish a peer connection from MicroShift, we encounter the following error messages:

TunnelEndpointNotFound: The TunnelEndpoint has not been found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
APIServerNotReady: The remote cluster API Server is not ready.
ResourceRequestPending: The remote cluster has not created a ResourceOffer in the Tenant Namespace liqo-tenant-openshift-central-de3ed9 yet.
NoResourceRequest: No ResourceRequest found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
APIServerStatus: The remote cluster API Server is not ready.

Peering Conditions

The peering conditions for the OpenShift and MicroShift clusters are as follows:

ForeignClusterProcessable: This ForeignCluster seems to be processable.
NetworkStatus: The TunnelEndpoint has not been found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
AuthenticationStatus: The Identity has been correctly accepted by the remote cluster.
OutgoingPeering: The remote cluster has not created a ResourceOffer in the Tenant Namespace liqo-tenant-openshift-central-de3ed9 yet.
IncomingPeering: No ResourceRequest found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
APIServerStatus: The remote cluster API Server is not ready.

Relevant Log Output

The relevant log output for this issue is as follows:

INFO  Peering enabled                                                                                                                                                                                          
 INFO  Authenticated to cluster "openshift-central"                                                                                                                                                             
 ERRO  Failed activating outgoing peering to the remote cluster "openshift-central": timed out waiting for the condition

Solution

To resolve this issue, we need to ensure that the remote cluster API Server is ready and that the TunnelEndpoint has been created in the Tenant Namespace. We also need to verify that the ResourceOffer has been created in the Tenant Namespace.

Here are the steps to resolve this issue:

Verify the remote cluster API Server: Ensure that the remote cluster API Server is ready and accessible.
Create the TunnelEndpoint: Create the TunnelEndpoint in the Tenant Namespace.
Verify the ResourceOffer: Verify that the ResourceOffer has been created in the Tenant Namespace.
Activate outgoing peering: Activate outgoing peering to the remote cluster.

Conclusion

In this article, we explored the issue of establishing a peer connection between OpenShift and MicroShift clusters using liqo. We identified the error messages, peering conditions, and relevant log output to determine the root cause of the problem. We provided a solution to resolve this issue by verifying the remote cluster API Server, creating the TunnelEndpoint, verifying the ResourceOffer, and activating outgoing peering.

Troubleshooting Tips

Here are some additional troubleshooting tips to help resolve this issue:

Check the liqo logs: Check the liqo logs for any errors or warnings that may indicate the root cause of the problem.
Verify the cluster configurations: Verify that the cluster configurations are correct and that the clusters are properly configured.
Check the network connectivity: Check the network connectivity between the clusters to ensure that they are properly connected.

Related Issues

Here are some related issues that may be helpful in resolving this problem:

Liqo documentation: Refer to the liqo documentation for more information on setting up a multi-cluster environment.
Kubernetes documentation: Refer to the Kubernetes documentation for more information on setting up a Kubernetes cluster.
OpenShift documentation: Refer to the OpenShift documentation for more information on setting up an OpenShift cluster.

Code of Conduct

This project follows the Kubernetes Code of Conduct. By contributing to this project, you agree to follow this Code of Conduct.

Acknowledgments

Introduction

In our previous article, we explored the issue of establishing a peer connection between OpenShift and MicroShift clusters using liqo. We identified the error messages, peering conditions, and relevant log output to determine the root cause of the problem. In this article, we will provide a Q&A section to help answer common questions related to this issue.

Q: What is the root cause of the problem?

A: The root cause of the problem is the inability to establish a peer connection between OpenShift and MicroShift clusters due to the TunnelEndpoint not being found in the Tenant Namespace.

Q: What are the error messages that indicate the problem?

A: The error messages that indicate the problem are:

TunnelEndpointNotFound: The TunnelEndpoint has not been found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
APIServerNotReady: The remote cluster API Server is not ready.
ResourceRequestPending: The remote cluster has not created a ResourceOffer in the Tenant Namespace liqo-tenant-openshift-central-de3ed9 yet.
NoResourceRequest: No ResourceRequest found in the Tenant Namespace liqo-tenant-openshift-central-de3ed9.
APIServerStatus: The remote cluster API Server is not ready.

Q: How can I resolve the issue?

A: To resolve the issue, you need to:

Verify the remote cluster API Server: Ensure that the remote cluster API Server is ready and accessible.
Create the TunnelEndpoint: Create the TunnelEndpoint in the Tenant Namespace.
Verify the ResourceOffer: Verify that the ResourceOffer has been created in the Tenant Namespace.
Activate outgoing peering: Activate outgoing peering to the remote cluster.

Q: What are the troubleshooting tips to help resolve the issue?

A: Here are some additional troubleshooting tips to help resolve the issue:

Check the liqo logs: Check the liqo logs for any errors or warnings that may indicate the root cause of the problem.
Verify the cluster configurations: Verify that the cluster configurations are correct and that the clusters are properly configured.
Check the network connectivity: Check the network connectivity between the clusters to ensure that they are properly connected.

Q: What are the related issues that may be helpful in resolving this problem?

A: Here are some related issues that may be helpful in resolving this problem:

Liqo documentation: Refer to the liqo documentation for more information on setting up a multi-cluster environment.
Kubernetes documentation: Refer to the Kubernetes documentation for more information on setting up a Kubernetes cluster.
OpenShift documentation: Refer to the OpenShift documentation for more information on setting up an OpenShift cluster.

Q: What is the Code of Conduct for this project?

A: This project follows the Kubernetes Code of Conduct. By contributing to this project, you agree to follow this Code of Conduct.

Q: How can I get help with this issue?

A: You can get help with this issue by:

Checking the liqo documentation: Refer to the liqo documentation for more information on setting up a multi-cluster environment.
Checking the Kubernetes documentation: Refer to the Kubernetes documentation for more information on setting up a Kubernetes cluster.
Checking the OpenShift documentation: Refer to the OpenShift documentation for more information on setting up an OpenShift cluster.
Reaching out to the liqo community: Reach out to the liqo community for help and support.
Filing a bug report: File a bug report if you are experiencing issues with liqo.

Conclusion

In this article, we provided a Q&A section to help answer common questions related to the issue of establishing a peer connection between OpenShift and MicroShift clusters using liqo. We hope that this article has been helpful in resolving this issue and providing a better understanding of the liqo project.