50k limit on ManifestWork not enough to define larger/more complex add-ons

[dangorst1066]

The current add-on framework creates a single ManifestWork that includes all the resources the add on requires to run in the managed clusters.

There is a 50k limit on the size of a ManifestWork resource set here which creates a problem when attempting to deploy more complex add ons , that define many resources. A single CRDs can easily exceed 50k on it's own - for example kustomizations.kustomize.toolkit.fluxcd.io is 60k.

Suggestion is to make the limit on a single ManifestWork configurable (primarily for large CRDs or ConfigMaps) AND update the addon controller to create a ManifestWork per resource (or similar) rather than bundling them all together into a single ManifestWork.

[qiujian16]

/assign @qiujian16
/kind bug

cc @zhiweiyin318

[openshift-ci]

@qiujian16: The label(s) kind/bug cannot be applied, because the repository doesn't have them.

In response to this:

/assign @qiujian16
/kind bug

cc @zhiweiyin318

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[qiujian16]

fixed by #122

[qiujian16]

/close

[openshift-ci]

@qiujian16: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.