Telepresence is a powerful tool designed to facilitate local development of applications that run in Kubernetes clusters. It allows developers to run a single service locally while connecting it to a remote Kubernetes cluster, providing a seamless development experience. This tool is particularly useful for debugging and testing microservices in a real-world environment without the need to deploy them to the cluster.
When using Telepresence, you might encounter the error message: telepresence: error 35. This error typically indicates an issue with the cluster's ingress configuration, which can prevent Telepresence from establishing a proper connection to the cluster.
Error 35 is often related to misconfigurations in the cluster's ingress settings. Ingress is a collection of rules that allow external access to services within a Kubernetes cluster. If these settings are incorrect, Telepresence may fail to route traffic correctly, resulting in this error.
To resolve this issue, follow these steps to verify and correct your ingress settings:
Ensure that your ingress controller is correctly installed and running. You can check the status of the ingress controller using:
kubectl get pods -n ingress-nginx
Look for any pods that are not running or have errors.
Review your ingress rules to ensure they are correctly configured. Use the following command to list all ingress resources:
kubectl get ingress
Inspect the output for any misconfigurations in the host, path, or service name.
Network policies might be restricting ingress traffic. Check your network policies with:
kubectl get networkpolicy
Ensure that the policies allow traffic to the necessary services.
For more detailed guidance on configuring ingress in Kubernetes, refer to the official Kubernetes Ingress Documentation. Additionally, the Telepresence Documentation provides further insights into troubleshooting common issues.
(Perfect for DevOps & SREs)
(Perfect for DevOps & SREs)
