Introduction of client3 causes connectivity test from starting on 2 node kind cluster, but works for 2 node minikube cluster

[jspaleta]

Bug report

So this is an interesting corner case single node deployments, like the documented minikube install work fine as there is some logic in the cilium-cni code that detects that client3 shouldn't attempt to be installed.

But for 2 node kind cluster, with a control-plane and a single worker, the client3 deployment gets attempted and basically hangs and evetually times outs because it can't get scheduled.

A 2 node minikube cluster doesn't have the problem, its a bit of a head scratcher.

General Information

• Cilium CLI version (run cilium version)

  $ cilium version
  cilium-cli: v0.16.8 compiled with go1.22.3 on darwin/arm64
  cilium image (default): v1.15.5
  cilium image (stable): v1.15.5

How to reproduce the issue

1. install kind with 2 nodes using:

   kind: Cluster
   apiVersion: kind.x-k8s.io/v1alpha4
   name: test
   nodes:
   - role: control-plane
   - role: worker
   networking:
   disableDefaultCNI: true

   kind create cluster --config test-config.yaml

2. install cilium cilium install --version 1.15.5
3. run connectivity tests
4. Notice that client3 deployment is attempted but fails
5. cry
6. repeat with 2 node minikube minikube start --cni cilium -n 2
7. run connectivity tests
8. watch client3 deployment succeed and wonder about life decisions that led you here

[jspaleta]

I should note the minikube is installing cilium v1.15.3, while kind is installing v1.15.5. I can't find a way to have minikube startup without a CNI present to do a traditional self install of cilium. So its not a perfect naranjas to oranges comparison between kind and minikube.

But I'm hoping the logic as to whether or not client3 deployment is attempted is something in cilium-cli logic, and it just needs to taste test the cluster node arrangement to figure out if it should be done.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.