Error with multiple kubeconfigs specified does not cease execution

[ikegentz]

Which version of kubefirst are you using?

2.7.9

Which cloud provider?

Vultr

Which DNS?

Cloudflare

Which installation type?

CLI

Which distributed Git provider?

GitHub

Did you use a fork of gitops-template?

No

Which Operating System?

Linux

What is the issue?

If you have your KUBECONFIG set to include paths to multiple config files, an error will be generated when running (in my case) kubefirst beta vultr create ... asking that you only have a single path entry set in this variable. Execution will continue however, and it seems to just be some general unedfined behavior. Verbose logs stop showing, and Terraform apply will silently fail. In the case of Vultr anyways, none of the block storage volumes get created, which then causes vault to fail. The kubefirst beta vultr create ... command will eventually then get stuck waiting on Vault and finally fail, due to this underlying issue.

I believe the simple fix is just to ensure that if this error log comes about due to multiple paths being set in KUBECONFIG, make sure to exit and cease execution.

I've confirmed that the fix is simply to ensure that KUBECONFIG is set to just ~/.kube/config, and then everything spins up as expected

Code of Conduct

• I agree to follow this project's Code of Conduct

[linear]

KON-61 Error with multiple kubeconfigs specified does not cease execution

[ikegentz]

Edit to above, it got much further however Vault is still failing to come up. I believe this is unrelated though, the original issue of not exiting and getting messed up still stands

[ikegentz]

Edit to above, it got much further however Vault is still failing to come up. I believe this is unrelated though, the original issue of not exiting and getting messed up still stands

My vault issue was unrelated and I opened a different issue for it

[fharper]

@ikegentz thanks for reporting this issue. I'll ask the engineering team to give it a closer look.