hermes 7364734713 fix(ci): count the kubeconfig's clusters correctly ...

The cluster-count guard I added used `grep -c '"name"'`, which counts
LINES.  The jsonpath output is a single line, so the count was 1 for a
kubeconfig with clusters and 1 for one without - which made the guard
reject every kubeconfig:

    ERROR: the kubeconfig has no cluster entries.

The count is now done with `grep -o . | wc -l`, which counts occurrences
rather than lines.  Tested against both cases:

- a real kubeconfig with a stale CA -> the CA is refreshed and kubectl works
- a kubeconfig with no clusters        -> refuses with a clear message

2026-11-09 12:21:07 +10:00

..

cluster-ca.sha256

fix(ci): pin the cluster CA in the repo rather than in a secret

2026-11-09 12:13:27 +10:00

kube-ca-refresh.sh

fix(ci): count the kubeconfig's clusters correctly

2026-11-09 12:21:07 +10:00