k8s-triage-robot
commented
2 years ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
kundan2707
sunjayBhatia
k8s-ci-robot
Currently the tests wait for the status of the Ingress resource created for the test case to be updated with an address before sending HTTP requests.
As far as I know, the status/address update isn't specified anywhere in the API as something that is required to be updated strictly before traffic can be sent to the services an Ingress references.
If this is true, the tests have added an implicit requirement that not all Ingress controllers may implement.
e.g. running the conformance suite against Contour is quite flaky as Contour updates the status on Ingress resources asynchronously, not strictly before it programs the routes on an Ingress
To fix this, it would be nice if the test requests are retried or a longer wait is configurable to ensure routes are actually programmed by an Ingress controller before sending requests (the retry option is maybe easier to tune/implement cleanly?)