Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

configure-istio: Improve error message when no ingress ip could be determined #157

Closed
christian-kreuzberger-dtx opened this issue Jan 25, 2021 · 0 comments · Fixed by #170
Assignees

Comments

@christian-kreuzberger-dtx
Copy link
Member

After installing istio it takes a couple of seconds before an Ingress IP can be determined. This is okay, though our error message suggests that something is wrong.

$ ./configure-istio.sh
Configure Istio and Keptn
INGRESS_IP is empty. Make sure that the Ingress gateway is ready

I believe we should adapt the code-snippet below

# Check if IP-Address is not empty or pending
if [ -z "$INGRESS_IP" ] || [ "$INGRESS_IP" = "Pending" ] ; then
echo "INGRESS_IP is empty. Make sure that the Ingress gateway is ready"
exit 1
fi

such that it prints:

  1. The kubectl command to verify what is going on
  2. General advice, that if IP adress is pending for more than 5 minutes, something is wrong (e.g., no load balancer is available)
  3. Link to the istio docs for more information
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant