the Helm chart is only lint-checked, so a bad template, a missing RBAC verb, or a probe misconfig (see #82, #105) only surfaces on a real cluster.
propose: an integration test that boots the testcontainers k3s module, helm installs the chart, and asserts the DaemonSet rolls out and /healthz responds. drive helm via its Go SDK (helm.sh/helm/v3) or a pinned helm exec, and assert pod/daemonset state with client-go. this validates the manifests end-to-end and would catch RBAC or probe regressions before release.
depends on the harness issue (#143), shares the k3s setup with #145.
the Helm chart is only lint-checked, so a bad template, a missing RBAC verb, or a probe misconfig (see #82, #105) only surfaces on a real cluster.
propose: an integration test that boots the testcontainers
k3smodule,helm installs the chart, and asserts the DaemonSet rolls out and/healthzresponds. drive helm via its Go SDK (helm.sh/helm/v3) or a pinned helm exec, and assert pod/daemonset state withclient-go. this validates the manifests end-to-end and would catch RBAC or probe regressions before release.depends on the harness issue (#143), shares the k3s setup with #145.