Handle lack of CRDs gracefully for every controller

[czeslavo]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Currently, KIC verifies the existence of CRDs installation in the cluster only for part of its resources' controllers. It uses crdExistsChecker in AutoHandler field of the ControllerDef struct to do that. Its job is to ensure that a given CRD exists in the cluster, and if not, to disable the controller completely. For the other controllers which don't use crdExistsChecker, behavior is different and falls back to a default one of runtime-controller upstream: controller awaits for cache to synchronize, but while CRD doesn't exist, it timeouts after default 2 minutes and crashes the whole process (see Kong/gateway-operator#326).

Proposed Solution

Make sure that all controllers have a uniform way of handling the lack of required CRDs (log the fact of disabling a controller and don't crash the process).

Further work

• Start custom resource controllers when the CRD appears after KIC startup #3029

Acceptance Criteria

• While any resource controller is missing required CRD installation, it is automatically disabled
• While a resource controller is disabled due to missing CRD installation, the event is explicitly logged in a uniform way common for every controller