-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New flag to allow option for passing a config file for addon configure command. #20255
base: master
Are you sure you want to change the base?
Conversation
instead of forcing prompts Fixes kubernetes#20124
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: panyam The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @panyam. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
Can one of the admins verify this patch? |
This comment has been minimized.
This comment has been minimized.
cmd/minikube/cmd/config/configure.go
Outdated
// Processes registry-creds addon config from configFile if it exists otherwise resorts to default behavior | ||
func processRegistryCredsConfig(profile string, configFileData map[string]any) { | ||
// Default values | ||
awsAccessID := "changeme" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there reason for "changeme" default value? seems unconventional, I would prefer either "" or something very explicit that has no chance of clodiing with users real values, like "MINIKUBE_DEFAULT_VALUE"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I like the MINIKUBE_DEFAULT_VALUE as a default. Updated it. PTAL
…ance to interfere with other possible user defaults
Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages. The list of commits with invalid commit messages:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
kvm2 driver with docker runtime
Times for minikube start: 50.5s 51.3s 47.5s 49.6s 46.8s Times for minikube ingress: 18.6s 15.4s 14.5s 16.0s 15.0s docker driver with docker runtime
Times for minikube start: 21.5s 23.9s 23.4s 24.1s 24.6s Times for minikube ingress: 12.7s 12.3s 12.3s 12.8s 12.8s docker driver with containerd runtime
Times for minikube ingress: 39.8s 38.8s 27.9s 28.8s 22.9s Times for minikube start: 20.0s 23.6s 23.4s 23.1s 23.0s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests:
To see the flake rates of all tests by environment, click here. |
Minor UI Change (Before and After described in the ticket) but tl;dr:
BEFORE
Currently when configuring addons with the command:
eg:
The user is prompted to input the values one by one, eg:
and so on. This makes it hard to store/load values in a scripted environemnt. Some times it easier to provide a config file containing so that the values can be read from this.
AFTER
Add a "-f" local flag to the addon configure command, eg:
etc
Fixes #20124