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

Grafana on Ambassador (Public DNS)? #2591

Closed
sam-zen-dev opened this issue Nov 2, 2020 · 3 comments
Closed

Grafana on Ambassador (Public DNS)? #2591

sam-zen-dev opened this issue Nov 2, 2020 · 3 comments
Labels
triage Needs to be triaged and prioritised accordingly

Comments

@sam-zen-dev
Copy link

Seldon has default setup for ambassador + namespace + modelName+ prediciton... and if i deployed on AWS EKS, it can be reached by using public DNS.

Since seldon has other UI pages like Grafana, Prometeus, Kubeflow. is it possible to custom config the ambassador and deploy multiple (4 UI pages here) using the one or multiple Ambassador?

any example?

@sam-zen-dev sam-zen-dev added the triage Needs to be triaged and prioritised accordingly label Nov 2, 2020
@ukclivecox
Copy link
Contributor

Can you explain your requirement further with an example?

@sam-zen-dev
Copy link
Author

Thanks, so for the deployed model in seldon namespace. we can use this URL to see the Swagger UI page.
http:///seldon///api/v1.0/docs
and is the Public DNS i have in AWS once i installed Ambassador in EKS.

Since Seldon also has other UI pages like Grafana and i am currently accessing it locally using Kubectl port-forward.... what i need is to be able to access Grafana, Premetheus, kubeflow also using the same configration like
http:///seldon//..... (Grafana or Prometheus, Kubeflow) ...

is there any Yaml template for me to re-config Ambassador or Istio?

@ukclivecox
Copy link
Contributor

We don't have a central config for these as for example the Grafana metrics is an example and should be managed by your organisation's access to Grafana. Similarly, for Kubeflow or Prometheus.

If you create a nice solution we'd like to hear about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

2 participants