-
Notifications
You must be signed in to change notification settings - Fork 173
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
Latest zarf version (0.26.3 as well) cannot deploy package without k8s present #1723
Comments
Will get a PR up for this asap - as a workaround though you can rename your |
Yes, confirmed removing ~/.kube/config is a workaround! The package continues to deploy after doing that. Thanks for the suggestion, your super quick response, and the pending PR! |
No problem! Submitted that PR and it should make it's way out in v0.27.0. Thanks for the report! |
…1724) ## Description This fixes an issue where an inaccessible cluster in a kube config can prevent the arch check ## Related Issue Fixes #1723 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [x] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
Environment
Device and OS: Linux (RHEL 8)
App version: 0.26.4
Kubernetes distro being used: k3s
Other:
Steps to reproduce
Expected result
Package deploys successfully
Actual Result
Running on the same exact package:
Zarf 0.26.1, package deploys successfully and doesn't need to contact k8s api
Zarf 0.26.4, package stops before even listing preview indicating it can't conect to https://127.0.0.1:6443/api/v1/nodes
There are no action in this zarf package that make usage of kubectl or need to query the k8s api server. The very last action is to systemctl start k3s-agent.
Visual Proof (screenshots, videos, text, etc)
Working:
Not Working:
Severity/Priority
Additional Context
This seems like a new behavior and not sure if this is intended. We would like to be able to run this without a k3s server since this is meant to stand up a k3s agent.
Here is a trace dump as well of the non-working:
The text was updated successfully, but these errors were encountered: