Use passed in credentials to deploy instead of getting the local kube config #524
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.
The openshiftt Rest client already has the ability to specify a username/password/api server url combo instead of using the default
~/.kube/config
file.This PR adds the ability to now pass those options in through the cli and API
New options added:
username
,password
,apiServer
andinsecure
.Since this flow doesn't get any existing kube configs that might be local, it will not get the current namespace/project that a user might be on. So by default it will just use the
default
namespace, but by using thenamespace
flag, it can easily be changed.If using Code Ready Containers(CRC), the cli command might look something like this:
$ nodeshift --apiServer https://api.crc.testing:6443 --username developer --password developer --insecure --namespace.name nodejs-examples
Still need to add tests and update the readme as well as not hard code the insecureTLSVerify variable for self-signed certs