Coredns and Calico Controller pods fail with dial tcp i/o timeout

We set up the k8s cluster in Redhat 8.9 with the below versions.
Kubernetes 1.27
Containerd 1.6
Calico 3.25.1
But the calico controller and coredns pods fail to start due to the below issue.

Pod Logs:

kubectl logs calico-kube-controllers-674fff74c8-tf4vg -n kube-system

2024-04-26 19:48:51.630 [INFO][1] main.go 107: Loaded configuration from environment config=&config.Config{LogLevel:“info”, WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:“”, DatastoreType:“kubernetes”}
W0426 19:48:51.631240 1 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2024-04-26 19:48:51.631 [INFO][1] main.go 131: Ensuring Calico datastore is initialized
2024-04-26 19:49:21.632 [ERROR][1] client.go 290: Error getting cluster information config ClusterInformation=“default” error=Get "
dial tcp i/o timeout
2024-04-26 19:49:21.632 [INFO][1] main.go 138: Failed to initialize datastore error=Get "":
dial tcp i/o timeout

Please let me know if any additional information is required and help us to resolve this.