Kubernetes > Ingress/Knative endpoint generation notice
When the endpoint is being generated for either Ingress or Knative we show the following warning message:
Problem
The text does not help the user determine what is wrong. It's unclear what "a long time is". Its unclear how to check quotas. It also doesn't mention a third option about Google having disruptions.
Solution
-
We should update the text of the warning message to give the user a sense of how long "a long time is". -
There are 3 known reasons for why the IP address may not generate or may take longer than expected. These are rare cases. I propose we simplify the text, and add all the reasons to the documentation. -
Update to use our alert styling. bs-callout bs-callout-alert
The endpoint is in the process of being assigned. If it takes longer than a few minutes, review our troubleshooting documentation.
-
Update documentation text (fixed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26303):
### Let GitLab fetch the external endpoint
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/17052) in GitLab 10.6.
If you [installed Ingress or Knative](https://22222.qa-tunnel.gitlab.info/help/user/project/clusters/index.md#installing-applications), you should see the Endpoint on this same page within a few minutes. If you don't see this:
1. Check your [Kubernetes cluster on Google Kubernetes Engine](https://console.cloud.google.com/kubernetes) to ensure there are no errors.
1. Ensure you have enough [Quotas](https://console.cloud.google.com/iam-admin/quotas) on Google Kubernetes Engine. [More information](https://cloud.google.com/compute/quotas)
1. Check [Google Cloud's Status](https://status.cloud.google.com/) to ensure they are not having any disruptions.
If GitLab is still unable to determine the Endpoint of your Ingress or Knative application, you can manually determine it by following the steps below.
Edited by Taurie Davis