Additionally include the following changes:
1. Include separate logger for the package
2. Switch to a status map to keep track of FeatureGate status.
This enables tracking multiple feature gates in the reconcile loop
and avoid calling the Kube API for individual feature gates

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Queries the K8s api to check if feature configmap
is present or not

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

OpenShift supports image layering, that allows deployment of packages by
providing a custom RHCOS image.
You need to create a MachineConfig with the custom RHCOS image url and
that's about it.

This commit adds support for using custom RHCOS image url to deploy Kata
components as an alternative to using the extension mechanism.

This capability is behind a feature gate and you'll need to set
LayeredImageDeployment to true in osc-feature-gates ConfigMap.

Additionally you'll need to set additional config params like shown
below for the layeredimagedeployment-config configmap:

apiVersion: v1
kind: ConfigMap
metadata:
name: osc-feature-gates
namespace: openshift-sandboxed-containers-operator
data:
LayeredImageDeployment: "true"

---

apiVersion: v1
kind: ConfigMap
metadata:
name: layeredimagedeployment-config
namespace: openshift-sandboxed-containers-operator
data:
osImageURL: "quay.io/...."
kernelArguments: "a=b c=d ..."

Logs an error and reconcile if LayeredImageDeployment
feature is enabled and configmap is not provided

Fixes: #KATA-2902

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

With the previous code of predicate func, the reconcile loop was
not receiving the KataConfig struct. Instead the reconcile loop was
called with the OSC featuregate configmap struct.
The new method ensures that for featuregate configMap changes,
the reconcile loop is called with the KataConfig struct.

Fixes: #KATA-2902, #KATA-2903
Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Modify createRuntimeClass function to createRuntimeClasses
This lays the foundation to support different runtimeClasses
for CoCo like kata-cc-tdx, kata-cc-snp, kata-cc-remote etc.

Fixes: #KATA-2903

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

This is enabled via AdditionalRuntimeClasses feature gate.
Example configuration is shown below:

apiVersion: v1
kind: ConfigMap
metadata:
  name: osc-feature-gates
  namespace: openshift-sandboxed-containers-operator
data:
  AdditionalRuntimeClasses: "true"

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: additionalruntimeclasses-config
  namespace: openshift-sandboxed-containers-operator
data:
  runtimeClassConfig: "name1:cpuOverHead1:memOverHead1, name2:cpuOverHead2:memOverHead2"
  #runtimeClassConfig: "name1, name2"

Also rearrange the code to have all the runtimeClass handling in a
single code file for easier readability

This feature typically will be used with other features.
For example this feature can be used with the image based deployment feature as well.
The image based deployment might have configuration for multiple
runtimeclasses which is then exposed to users as RuntimeClass objects
created by OSC operator when this feature gate is enabled.

Logs an error if AdditionalRuntimeClasses feature is enabled
and config is not provided

Fixes: #KATA-2903
Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Add examples for LayeredImageDeployment and
AdditionalRuntimeClasses feature

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

IsEnabled method is no longer needed. Hence removing it

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

This aligns with its usage

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Featuregate status configmap is initialised by the operator
itself.

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Check for featuregate status configmap in the beginning of the reconcile
loop and don't proceed if it's missing

This ensures we don't take any action if we cannot determine the
FeatureGateStatus which could be due to an error in fetching the
ConfigMap or the ConfigMap not being present

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

We had different methods to read yaml files depending on the
kubernetes object. However this is really not needed as all the methods
simply were reading files with the only difference being the flie
location.
This commit simplifies the code and uses a single readYamlFile method.
The caller should set the full path of the yaml file to be read.
Further any additional requirements to read different yaml files will
no longer need a new method

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

This avoids confusion with the individual feature gate configmap
and also correctly reflects the intent of the variable

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Since fg status configmap is must and created during operator
initialisation, we need to ensure on KataConfig deletion it's reverted
back to default values.

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>

Signed-off-by: Pradipta Banerjee <pradipta.banerjee@gmail.com>