Ambassador service is not being created - Azure deployment

[yuval-yaari]

Either the documentation is out of date, or there is an issue with the installation.
I'm trying to follow the Azure installation instructions, and it states to expose a service called ambassador.
Such service is not created in the kubeflow namespace.

[issue-label-bot]

Issue-Label Bot is automatically applying the label kind/bug to this issue, with a confidence of 0.85. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[sarahmaddox]

This is the likely doc:
https://www.kubeflow.org/docs/azure/deploy/install-kubeflow/

We've updated the portforwarding instructions for other deployments:
https://www.kubeflow.org/docs/other-guides/accessing-uis/#using-kubectl-and-port-forwarding
kubectl port-forward -n istio-system svc/istio-ingressgateway 8080:80

/assign @gopitk

[k8s-ci-robot]

@sarahmaddox: GitHub didn't allow me to assign the following users: gopitk.

Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

This is the likely doc:
https://www.kubeflow.org/docs/azure/deploy/install-kubeflow/

We've updated the portforwarding instructions for other deployments:
https://www.kubeflow.org/docs/other-guides/accessing-uis/#using-kubectl-and-port-forwarding
kubectl port-forward -n istio-system svc/istio-ingressgateway 8080:80

/assign @gopitk

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.

[jtfogarty]

/area docs
/priority p2

[jlewi]

Ambassador is no longer used. We now use ISTIO.
Closing this as obsolete.