-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
make oadm router and registry resiliant to missing client #18546
make oadm router and registry resiliant to missing client #18546
Conversation
return fmt.Errorf("can't check for existing docker-registry %q: %v", name, err) | ||
} | ||
if opts.Config.Action.DryRun { | ||
return fmt.Errorf("Docker registry %q service does not exist", name) |
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.
nit: docker-registry
/lgtm |
8f8df53
to
e1e8acf
Compare
Reworked to add a @mfojtik take another look? |
3b12470
to
a509e41
Compare
/assign @mfojtik prereq for cluster up |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, mfojtik The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 18437, 18546, 18550, 18579). |
oc adm router --dry-run -o yaml
(and registry) shouldn't require an apiserver connection. This makes it tolerant for cluster up