-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Log console URL at end of install, as well as initial user info #782
Comments
kubeadmin
's password
@sallyom, can I assign this to you? Or do we need to find someone else to implement it? |
@wking I think we'll have to pick it up. Do you have time today? :) |
I’m planning on doing that by tomorrow am.. but if you beat me to it that’s
fine :)
On Wed, Dec 5, 2018 at 7:01 PM Alex Crawford ***@***.***> wrote:
@wking <https://github.com/wking> I think we'll have to pick it up. Do
you have time today? :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#782 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKphcafXnnYZA9UcVQc7WLE5QjFegWGCks5u2F5tgaJpZM4ZBPI0>
.
--
SALLY ANN O'MALLEY
SOFTWARE ENGINEER
Red Hat
<https://www.redhat.com/>
somalley@redhat.com
<https://red.ht/sig>
|
/assign @sallyom |
@sallyom let me know if there is anything you need from me to make this happen. I'm guessing we may need some console adjustments. |
|
Can't you pull the route from the cluster? We aready have a kube client for the event-watcher. |
I was curious about that, if it should come from I have some work to do on getting the operator status public url published out, but if that's the route to take let me know so I can unblock. |
@benjaminapetersen I grabbed Spec.Host from the route 👍 |
ok great that works! |
master
Platform (aws|libvirt|openstack): all
Opening an issue to track this requirement:
At end of install, log information to user about the kubeadmin user/password and the console URL for which the kubeadmin user will have access to.
The text was updated successfully, but these errors were encountered: