On a fkb-master-kubernetes-jammy-cilium-aws run, we get the juju status message of `Waiting for 1 kube-system pod to start`, this pod remains in a pending stage due to Cilium not being up, however with no indication of it being down from the Juju unit logs or journalctl.
From syslog:
313270:Sep 23 15:39:41 ip-172-31-44-7 kubelet.daemon[128699]: E0923 15:39:41.596029 128699 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"CreatePodSandbox\" for \"ebs-csi-node-zjb2x_kube-sy
stem(53ed6a1a-7a61-43a7-a96c-2f08f628784c)\" with CreatePodSandboxError: \"Failed to create sandbox for pod \\\"ebs-csi-node-zjb2x_kube-system(53ed6a1a-7a61-43a7-a96c-2f08f628784c)\\\": rpc error: code = Unknown
desc = failed to setup network for sandbox \\\"536bde7221aa9e9c03108286c9902973d696e0a396114d02aed2bdeba4c51394\\\": plugin type=\\\"cilium-cni\\\" name=\\\"cilium\\\" failed (add): unable to connect to Cilium
daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get \\\"http:///var/run/cilium/cilium.sock/v1/config\\\": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory\\
nIs the agent running?\"" pod="kube-system/ebs-csi-node-zjb2x" podUID="53ed6a1a-7a61-43a7-a96c-2f08f628784c"
Test run: https://solutions.qa.canonical.com/testruns/b7d6e114-f6ce-434e-a7c6-82341abc2966/
Artifacts: https://oil-jenkins.canonical.com/artifacts/b7d6e114-f6ce-434e-a7c6-82341abc2966/index.html
