SUSE Support

Here When You Need Us

Pods not able to connect to kube-apiserver

This document (000019641) is provided subject to the disclaimer at the end of this document.


SUSE Caas Platform


In CaaS Platform, pods cannot communicate to kube-apiserver.

e.g. kured prints the following error: 
time="2020-06-02T12:42:22Z" level=fatal msg="Error testing lock: Get dial tcp i/o timeout"
The keywords in above error message are:
dial tcp i/o timeout
Above error indicates that kured pod is not able to access the kubernetes default service. 


IPv4 forwarding needs to be enabled on all CaaS Platform machines. This can be changed without having to reboot by running the following:
sysctl -w net.ipv4.ip_forward=1
For persistence after reboot, add the following to /etc/sysctl.conf or to conf file in /etc/sysctl.d:
net.ipv4.ip_forward = 1


The issue could occur due to several reasons.  One such reason is that IPv4 forwarding is disabled on nodes.  IPv4 forwarding needs to be enabled on all CaaS Platform machines.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000019641
  • Creation Date: 04-Jun-2020
  • Modified Date:23-Oct-2020
    • SUSE Caas Platform

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.