Patryk Małek

Sure thing. Let's reopen if that flake reoccurs, however it's going to be detected.

Again: https://github.com/Kong/kubernetes-ingress-controller/runs/8211944549?check_suite_focus=true#step:6:3217

> Let's see if buildpulse if detects any flakes in `TestKongIngressEssentials` Didn't you mean to post it in https://github.com/Kong/kubernetes-ingress-controller/issues/2632 😅 ?

Recent occurrence: https://github.com/Kong/kubernetes-ingress-controller/runs/7747128878?check_suite_focus=true#step:5:957

Still occurring: https://github.com/Kong/kubernetes-ingress-controller/runs/7763856269?check_suite_focus=true#step:6:1043

Still failing: https://github.com/Kong/kubernetes-ingress-controller/runs/7880887179?check_suite_focus=true#step:5:723

This looks relatively easy to do with e.g. https://github.com/marketplace/actions/create-github-issue ```yaml steps: - uses: actions/checkout@v3 - name: Something that might fail run: exit 1 - name: Create Issue on Failed workflow...

I'd like to highlight the fact that despite us wanting to test KIC with nightly images of GW, we shouldn't strive to be obsessive about 100% of tests passing at...

One more comment: I do realize that it's hard to make e2e tests (that include components that we're cannot fully rely on) 100% reliable but having tests like these run...

I was trying to comment that failing test jobs (like recently e.g. [integration-tests-enterprise-postgres-nightly](https://github.com/Kong/kubernetes-ingress-controller/runs/7614033500?check_suite_focus=true#logs)) after failing for a while are "OK" and become white noise that we got used to. So...