fix: KUBECONFIG gets set when using --kubeconfig via var DEVSPACE_FLAGS #2860
Conversation
✅ Deploy Preview for devspace-docs canceled.Built without sensitive environment variables
|
336ba90 to
b254376
Compare
|
@FabianKramm, @LukasGentele would any of you guys mind reviewing this? |
|
@siredmar Can you take a look at the e2e test failures? |
|
TL;DR Would you mind re-running the pipeline? The failing e2e test seems like a problem with the OCI registry. Not sure if this is actually related to my change as both e2e tests for k8s 1.27.3 and 1.28.0 fail with the same error in different test cases both at exactly the same time (18:21:11). |
|
@lizardruss please trigger a re-run of the e2e tests. Thanks. |
Signed-off-by: Armin Schlegel <armin.schlegel@gmx.de>
b254376 to
d8978ac
Compare
|
Unsure why linting suddenly fails, but I can address those in a separate PR. |
What issue type does this pull request address? (keep at least one, remove the others)
/kind bugfix
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>if possible)resolves #2859
Please provide a short message that should be published in the DevSpace release notes
Environment variable
KUBECONFIGgets set when using--kubeconfigvia variableDEVSPACE_FLAGSwithin devspace.yamlWhat else do we need to know?