[BUG] Big resources fail to be applied by kustomize at startup.

[jmprusi]

What happened?

Added a big resource (https://github.com/openshift/operator-framework-olm/blob/master/manifests/0000_50_olm_00-clusterserviceversions.crd.yaml) to the manifests dir of microshift (/usr/lib/microshift/manifests.d/olm/....) and it wasn't created on microshift start or restart.

What did you expect to happen?

The CRD is to be created appropriately.

How to reproduce it (as minimally and precisely as possible)?

1. Create the directory for our manifests:

mkdir -p /usr/lib/microshift/manifests.d/olm

2. Get the CRD file and put it on the proper place...

curl -o /usr/lib/microshift/manifests.d/olm/crd.yaml https://raw.githubusercontent.com/openshift/operator-framework-olm/master/manifests/0000_50_olm_00-clusterserviceversions.crd.yaml

4. Create the kustomization.yaml file

cat <<EOF >> /usr/lib/microshift/manifests.d/olm/kustomization.yaml
> apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
  - crd.yaml
> EOF

5. restart microshift

systemctl restart microshift

6. try to get the crd:

oc get clusterserviceversions

Anything else we need to know?

Environment

• MicroShift version (use microshift version): MicroShift Version: 4.15.0-0.nightly-2023-10-26-120535-20231027190735-f58cbeea5-dirty
• Hardware configuration: ec2 m5.xlarge
• OS (e.g: cat /etc/os-release): Red Hat Enterprise Linux 9.2 (Plow)
• Kernel (e.g. uname -a): 5.14.0-284.11.1.el9_2.x86_64 Init #1 SMP PREEMPT_DYNAMIC
• Others:

Relevant logs

Apply creates a metadata.annotation that is too long.

The CustomResourceDefinition "clusterserviceversions.operators.coreos.com" is invalid: metadata.annotations: Too long: must have at most 262144 bytes