Skip to content

1.7 connectivity check YAML hostPort pods never become ready #11563

@joestringer

Description

@joestringer

Cilium v1.7.4 release testing, deployed via GKE instructions:

https://docs.cilium.io/en/v1.7/gettingstarted/k8s-install-gke/

$ kubectl apply -f https://raw.githubusercontent.com/cilium/cilium/v1.7/examples/kubernetes/connectivity-check/connectivity-check.yaml
...
$ kubectl get po | grep hostpo
pod-to-b-intra-node-hostport-6549fc5b88-lmjdv           0/1     Running   5          5m22s
pod-to-b-multi-node-hostport-795964f8c8-8k5nb           0/1     Running   3          5m20s
$ k describe pod/pod-to-b-multi-node-hostport-795964f8c8-8k5nb | tail -n 1
k  Warning  Unhealthy  48s (x24 over 4m38s)   kubelet, gke-joe-k-e-default-pool-14835e70-qhs1  Readiness probe failed: curl: (7) Failed to connect to echo-b-host-headless port 40000: Connection refused
$ kubectl get pods -o yaml | grep hostPo
        hostPort: 40000

^^^ echo-b pod appears to have hostPort configured.

Metadata

Metadata

Assignees

Labels

kind/bugThis is a bug in the Cilium logic.kind/questionFrequently asked questions & answers. This issue will be linked from the documentation's FAQ.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions