This repository was archived by the owner on Apr 10, 2024. It is now read-only.
Work around conflicts with existing kubeconfig file
#133
Conversation
This file contains hidden or 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
…rator-sdk#116 Signed-off-by: Jakub Scholz <[email protected]>
scholzj
deleted the
workaround-conflicts-with-existing-kubeconfig-file
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In some environments, where the user has an existing
kubeconfigfile with an active context using theclient-key-dataorclient-certificate-datafields, thekubectlclient used in the Kube API server readiness check does not know what certificates to use and the API Server startup fails with the exceptionJenvtestException: Kube API Server did not start properly.This PR works around it by specifying the
KUBECONFIGenvironment variable to an non-existent config file when callingkubectlin the readiness check. That makes thekubectlprocess not use the pre-existingkubeconfigwith its certificates and makes everything work.This is not needed is the user asks for updating the
kubeconfigfile as in such case, thekubeconfigalready contains the correct configuration and no special handling is needed.This should resolve #116