Skip to content
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

Update kube-up output to print v1beta3 URLs for system services #7016

Closed
roberthbailey opened this issue Apr 18, 2015 · 4 comments · Fixed by #7502
Closed

Update kube-up output to print v1beta3 URLs for system services #7016

roberthbailey opened this issue Apr 18, 2015 · 4 comments · Fixed by #7502
Assignees
Labels
area/api Indicates an issue on api area. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone

Comments

@roberthbailey
Copy link
Contributor

Right now at the end of ./cluster/kube-up.sh I get

Kubernetes master is running at https://130.211.151.243
elasticsearch-logging is running at https://130.211.151.243/api/v1beta1/proxy/services/elasticsearch-logging/ (note the trailing slash)
kibana-logging is running at https://130.211.151.243/api/v1beta1/proxy/services/kibana-logging/ (note the trailing slash)
kube-dns is running at https://130.211.151.243/api/v1beta1/proxy/services/kube-dns/ (note the trailing slash)
influxGrafana is running at https://130.211.151.243/api/v1beta1/proxy/services/monitoring-grafana/ (note the trailing slash)
heapster is running at https://130.211.151.243/api/v1beta1/proxy/services/monitoring-heapster/ (note the trailing slash)

We should update the output to point to the appropriate v1beta3 URL endpoints instead.

@roberthbailey roberthbailey added priority/backlog Higher priority than priority/awaiting-more-evidence. area/api Indicates an issue on api area. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels Apr 18, 2015
@roberthbailey
Copy link
Contributor Author

/cc @satnam6502

@bgrant0607
Copy link
Member

Ref #5475 and #6584. cc @nikhiljindal

@bgrant0607 bgrant0607 added this to the v1.0 milestone Apr 18, 2015
@satnam6502
Copy link
Contributor

And as a minor nit, not all of those URLs need a trailing slash hack e.g. I don't think it is required for Elasticsearch. I think @piosz most recently worked on this code?

@piosz piosz self-assigned this Apr 18, 2015
@bgrant0607 bgrant0607 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Apr 27, 2015
piosz added a commit to piosz/kubernetes that referenced this issue Apr 29, 2015
@roberthbailey
Copy link
Contributor Author

Thanks for fixing this @piosz!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Indicates an issue on api area. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants