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.

fix(chart): default kube-ovn-controller replicas to 1 in dataPlaneOnly

Discovered while bringing up a real Kamaji-style local environment
(kind + Kamaji + tenant docker worker via kubeadm join). On the tenant
cluster, controller-deploy.yaml's `replicas: {{ include "kubeovn.
nodeCount" . }}` triggered the helper's `fail` because tenant nodes
don't carry the `kube-ovn/role=master` label (Kamaji moves the control
plane into the management cluster as pods).

Add a kubeovn.controllerReplicas helper:
- dataPlaneOnly: default to 1 (active/standby HA is by leader election,
  not horizontal scale)
- everywhere else: keep nodeCount behaviour
- operators can override via `kube-ovn-controller.replicas`

controller-deploy.yaml now uses this helper. Verified end-to-end:
`helm install --kubeconfig=tenant-kc -f tenant-values.yaml` now
succeeds, the controller Deployment + ovs-ovn DS + kube-ovn-cni DS land
on the tenant worker, and the tenant worker's TCP path to the
management cluster's MetalLB VIP `172.18.255.210:6641/:6642` is open.

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