fix: KUBECONFIG gets set when using --kubeconfig via var DEVSPACE_FLAGS #2860
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for devspace-docs canceled.Built without sensitive environment variables
|
Signed-off-by: Armin Schlegel <[email protected]>
siredmar
force-pushed
the
fix/kubeconfig-devspace_flags
branch
from
336ba90
to
b254376
Compare
|
@FabianKramm, @LukasGentele would any of you guys mind reviewing this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?