Skip to content

fix: use KUBECONFIG or explicitly given kubeconfig file (#67) #69

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

Merged
merged 1 commit into from
May 5, 2025

Conversation

adietish
Copy link
Contributor

@adietish adietish commented May 5, 2025

fixes #67

Signed-off-by: Andre Dietisheim <adietish@redhat.com>
Copy link
Owner

@manusa manusa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thx!

@manusa manusa added this to the 0.1.0 milestone May 5, 2025 — with automated-tasks
@manusa manusa merged commit bcd7712 into manusa:main May 5, 2025
5 checks passed
@adietish adietish deleted the issue-67 branch May 5, 2025 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KUBECONFIG env variable not honored in npx child process
2 participants