Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

The kuttl cli overrides the testsuite file... with the exception of the test env. (this is a require to fix that).

If the kuttl-test.yaml has a configuration for startControlPlane: true and the cli is started with --start-kind.... the cli override should start kind.

Perhaps we should have an override that allows to point at a cluster (currently it is the default that is selected if no

This should be the UI endpoint not the API server.

Today we had an outage in Quay repository, which had a great impact in our CI since we pull the OLM image from it.

Would be better to cache this image with Docker service and load it every time instead of pulling it. Will decrease our CI processing time and will also prevent our workflow to face problems like this in the future.

Link for the outage: https://status.quay.io/incidents/kw2627b