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

Describe the bug
Currently we check our code with golangci-lint, which in itself catches most of the things, but having comments over exported function is not caught by it, it'll be nice to enable both the linters. Currently there are some warnings by this linter on the main branch

To Reproduce
Run: golint ./... | grep -v zz_generated #to ignore the auto-generated files

**Expe

Until projectcontour/contour-operator#18 is fixed, the operator does not support running multiple contour instances within the same namespace. However, the operator does not implement this restriction. This can lead to child resources of a Contour, i.e. Contour ConfigMap, being overwritten by a new Contour that specifies the same namespace as the current Contour.