You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of our environments, we have a cluster with v1.24.13+rke2r1 Kubernetes version.
Here they are running on SUSE Linux Enterprise Server 15 SP5 OS.
Routine OS security packages are updated and then the servers are restarted starting from worker nodes. In the last process, after the servers are restarted:
RKE2 Calico pods are down,
Here, there is v3.25.0 RKE2-Calico as CNI. All pods started to receive access errors and could not reach the 10.43.0.1 Kubernetes Service IP. Calico pods and other pods started giving the following error log:
"""
Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0126 13:44:56.288873 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2025-01-26 13:44:56.289 [INFO][1] main.go 131: Ensuring Calico datastore is initialized
2025-01-26 13:45:26.289 [ERROR][1] client.go 290: Error getting cluster information config ClusterInformation="default" error=Get "https://10.43.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.43.0.1:443: i/o timeout
2025-01-26 13:45:26.289 [INFO][1] main.go 138: Failed to initialize datastore error=Get "https://10.43.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.43.0.1:443: i/o timeout
"""
Selinux and firewalld were checked on the servers and no changes were made to the Network settings. System administrators have stated that no blocking updates have been made within the network.
If anyone has information on this issue or has encountered a situation, I would like to ask for your help.
The text was updated successfully, but these errors were encountered:
Kubernetes v1.24 has been end of life since August 2023. Please upgrade to a supported release. Newer RKE2 releases are more likely to have been tested to be compatible with newer Linux distribution releases, for specific information check the support matrix.
In one of our environments, we have a cluster with v1.24.13+rke2r1 Kubernetes version.
Here they are running on SUSE Linux Enterprise Server 15 SP5 OS.
Routine OS security packages are updated and then the servers are restarted starting from worker nodes. In the last process, after the servers are restarted:
"""
Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0126 13:44:56.288873 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2025-01-26 13:44:56.289 [INFO][1] main.go 131: Ensuring Calico datastore is initialized
2025-01-26 13:45:26.289 [ERROR][1] client.go 290: Error getting cluster information config ClusterInformation="default" error=Get "https://10.43.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.43.0.1:443: i/o timeout
2025-01-26 13:45:26.289 [INFO][1] main.go 138: Failed to initialize datastore error=Get "https://10.43.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": dial tcp 10.43.0.1:443: i/o timeout
"""
If anyone has information on this issue or has encountered a situation, I would like to ask for your help.
The text was updated successfully, but these errors were encountered: