c0b76b168e
The pre-install Job runs before any CNI is installed, so all nodes are tainted NotReady-NoSchedule and the pod has no pod network. Without adjustment the Job's pod sits Pending until helm's pre-install timeout fires, blocking the entire install. Surfaced in PR #2500 CI run 25040584552 attempt 2: FailedScheduling 0/3 nodes are available: 3 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. Mirror the cozystack-operator deployment's scheduling pattern: - hostNetwork=true so the pod doesn't depend on CNI - Tolerations matching the operator (not-ready / unreachable / cilium.agent-not-ready / cloudprovider.uninitialized) - Variant-aware KUBERNETES_SERVICE_HOST/PORT env so kubectl reaches the apiserver before kube-proxy + CNI are up: talos: localhost:7445 (KubePrism) generic: cozystack.apiServerHost / Port hosted: default in-cluster Verified on the sandbox kind cluster that the rendered Job manifest schedules and the kubectl container starts (the kind cluster itself doesn't run KubePrism so the env-var path can't be end-to-end-tested there; the Talos E2E will exercise it). Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com> |
||
|---|---|---|
| .. | ||
| example | ||
| images/cozystack-operator | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| Makefile | ||
| values.yaml | ||