You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device and OS: Debian Bookworm (custom installer)
App version: Zarf v0.35.0
Kubernetes distro being used: zarf's own k3s
Steps to reproduce
We're creating a custom Debian installer with simple-cdd, include cloud-init (via deb), zarf, and the zarf-init-package and make cloud-init run "zarf init --components k3s --confirm --no-color --no-progress".
Expected result
k3s and the zarf stuff are installed, just as when I install them manually from the command line after a "pure" installation (which does work).
Actual Result
Zarf does install k3s, but fails to connect with the message "invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable". Accordingly, k8s is running but does not contain the zarf data.
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
We found a workaround. Setting KUBECONFIG=/etc/rancher/k3s/k3s.yaml makes the installation work.
Environment
Device and OS: Debian Bookworm (custom installer)
App version: Zarf v0.35.0
Kubernetes distro being used: zarf's own k3s
Steps to reproduce
We're creating a custom Debian installer with simple-cdd, include cloud-init (via deb), zarf, and the zarf-init-package and make cloud-init run "zarf init --components k3s --confirm --no-color --no-progress".
Expected result
k3s and the zarf stuff are installed, just as when I install them manually from the command line after a "pure" installation (which does work).
Actual Result
Zarf does install k3s, but fails to connect with the message "invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable". Accordingly, k8s is running but does not contain the zarf data.
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
The text was updated successfully, but these errors were encountered: