-
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
Prevent registry-creds configure from failing when a secret does not exist. #6380
Prevent registry-creds configure from failing when a secret does not exist. #6380
Conversation
Welcome @akshaysu12! |
Hi @akshaysu12. 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/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akshaysu12 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 |
Can one of the admins verify this patch? |
pkg/minikube/service/service.go
Outdated
if err != nil { | ||
return &retry.RetriableError{Err: err} | ||
} | ||
secret, _ := secrets.Get(name, meta.GetOptions{}) |
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.
At a minimum, this should log or display an error rather than hide it entirely. I'm not exactly sure which is appropriate here, but naively glog.Errorf?
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.
Thanks, logging makes sense. I feel a glog.Infof would be most appropriate as I don't think it should be an error when CreateSecrets is unable to get a secret it is going to create.
/ok-to-test |
Error: running mkcmp: exit status 1 |
…l when a secret does not exist.
fc3d288
to
2ba3116
Compare
Codecov Report
@@ Coverage Diff @@
## master #6380 +/- ##
==========================================
- Coverage 38.3% 37.46% -0.84%
==========================================
Files 124 128 +4
Lines 8355 8646 +291
==========================================
+ Hits 3200 3239 +39
- Misses 4737 4988 +251
- Partials 418 419 +1
|
OK to test |
/ok-to-test |
…l when a secret does not exist.
closes #5885