Ingress not visible immediately about serving

[mattmoor]

Ah, let's close this and open a new issue to track the second issue?

I think the root of what prompted this issue has been resolved (and thus the M4 scoped portion).

I think faster ingress is more aspirational (not M4) and the path unclear.

[mchmarny]

I'm not able to replicate this, kubectl get ing lists new ingress service right after deploying sample. @grantr can you check if the original issue is still there with the latest builds?

[mattmoor]

I believe this is because the latency is in creating a GCP load balancer, and subsequent Ingress use the same external IP (so it's faster).

[mattmoor]

I think we want to add a watch of the Route controller before we declare the Route ready.

[mattmoor]

@tcnghia the linked PR mentions that it partially fixes this. Can you please spell out what work is remaining?

[tcnghia]

The Ready Status that we added for Route is sufficient for the client to wait for the IP address, they don't need to rely on seeing the Ingress to do the wait.

However it would be nicer to have the Ingress appear faster. I am not sure if this is something we can do on our side (i.e. do we have a bug that causes Ingress to appear later than it should?). So the remaining work is to figure out if we do have such bug and fix it.

[tcnghia]

I think faster ingress is more aspirational (not M4) and the path unclear.

Yes, that sums it up correctly. Closing SGTM.