Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

test(kamaji): add end-to-end split-cluster Helm verification

Turn the manual Kamaji-on-kind walkthrough into a reproducible automated
e2e. The local validation covered the only flow that exercises both
halves of installMode together (controlPlaneOnly + dataPlaneOnly +
externalOvnCentral.endpoint), and CI/contributors need the same path.

- hack/kamaji-e2e.sh: subcommands `setup`, `teardown`, `kubeconfig`,
  `vars`. Brings up the mgmt kind cluster, installs cert-manager,
  MetalLB and Kamaji, installs kube-ovn `installMode=controlPlaneOnly`
  with single-replica + LoadBalancer + storage, creates a
  TenantControlPlane via Kamaji, spawns a privileged docker container
  for the tenant worker (with containerd's native snapshotter to dodge
  nested-overlayfs whiteout issues), pre-pulls the kube-ovn image via a
  local registry, joins the worker via kubeadm and installs
  `installMode=dataPlaneOnly` pointed at the management cluster's
  MetalLB VIP.

- test/e2e/kamaji/kamaji_test.go: a small Ginkgo suite that auto-skips
  when not running against a dataPlaneOnly tenant cluster. It verifies:
  (1) kube-ovn-controller defaults to replicas=1 (covers the
  kubeovn.controllerReplicas helper); (2) ovs-ovn really keeps an
  ESTAB connection to the external ovn-sb VIP via `ss` exec;
  (3) tenant Pods get IPs from the OVN subnet through the cross-cluster
  control path; (4) leader-election Lease lives on the tenant
  apiserver.

- makefiles/kind.mk: new `kind-install-kamaji` / `kind-clean-kamaji`
  targets that wrap the shell script.

- makefiles/e2e.mk: register `./test/e2e/kamaji` in `e2e-build` and add
  `kube-ovn-kamaji-e2e` target. The target sources KUBECONFIG and the
  KUBE_OVN_KAMAJI_MGMT_VIP env from `hack/kamaji-e2e.sh vars` so the
  Ginkgo suite can identify the external VIP without rediscovering it.

Reproducing locally:
  make build-dev
  make kind-install-kamaji
  make kube-ovn-kamaji-e2e
  make kind-clean-kamaji

Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>