-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading manifests without namespace specified fails #151
Comments
@ibuildthecloud I've got k3s building myself now so happy to try to send a PR for this one. |
@dpen2000 I went ahead and tried to fix this while I was fixing another bug, but it's not heavily tested. Do you want to give v0.2.0-rc6 a try and see if its working now? It should assign the namespace to "default" for namespaced resources where the namespace is "". |
@ibuildthecloud The example above works. As for helm charts, I tried:
which doesn't work for me. I don't get any error output about it either. This doesn't either:
Only specifiying kube-system seems to work:
Editing this chart to say |
Also verified that example nginx deployment works, created a new issue for Helm deployments. |
Describe the bug
K3s fails to load manifests from /var/lib/rancher/k3s/server/manifests if they don't specify a namespace.
To Reproduce
k3s server
in one terminal/var/lib/rancher/k3s/server/manifests/deployment.yaml
in another terminalExpected behavior
K3s should assume default namespace and create deployment as per kubectl apply
The text was updated successfully, but these errors were encountered: