Calico On EKS failing to Deploy
Summary
When deploying calico CNI with calico networking on EKS the kube-controller node is not starting up. Open internet containers startup without issue.
Steps to reproduce
https://docs.projectcalico.org/getting-started/kubernetes/managed-public-cloud/eks and apply https://docs.projectcalico.org/manifests/calico-vxlan.yaml but replace open internet images with latest Iron Bank Images
What is the current bug behavior?
Pod goes into crash loop backoff.
What is the expected correct behavior?
Pod starts up and communication can occur between pods on different nodes over the CNI.
Relevant logs and/or screenshots
Log messages from pod below. Looks similar to issue #1 (closed).
Warning Unhealthy 17s (x2 over 27s) kubelet Readiness probe failed: Failed to read status file /status/status.json: open /status/status.json: no such file or directory
W1110 23:56:46.375343 1 client_config.go:615] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2021-11-10 23:56:46.375 [INFO][1] main.go 115: Ensuring Calico datastore is initialized
2021-11-10 23:56:56.376 [ERROR][1] client.go 261: Error getting cluster information config ClusterInformation="default" error=Get "https://172.20.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded
2021-11-10 23:56:56.376 [FATAL][1] main.go 120: Failed to initialize Calico datastore error=Get "https://172.20.0.1:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded```
## Possible fixes
Might have to do with perms on the /status area?
## Defintion of Done
- [ ] Bug has been identified and corrected within the container