Separate CRD manifest

[ishioni]

Proposal

I would like a separate CRD-only yaml to deploy CRDs tak keda uses

Use-Case

I manage my cluster with flux, using their helmrelease CRDs and kustomize. This works fine but on the condition that CRDs are deployed on a separate step before the actual helm release. This is to combat the fact that helm releases in a kustomization step are run in parallel, and if any of them include keda resources, they will obviously fail until keda itself is installed.

Installing only the CRDs in a separate step neatly fixes this. Most projects that use CRDs that I've encountered (cert-manager, tigera) offer separate CRD yamls knowing that helm-managed CRDs are iffy

Anything else?

No response

[tomkerkhove]

Would you prefer to have them as a YAML file in that case?

[ishioni]

Yes, that would be ideal

[tomkerkhove]

Any thoughts on this @zroubalik?

[zroubalik]

Fine for me, the CRDs are already part of the big keda-2.X.X.yaml (eg. https://github.com/kedacore/keda/releases/download/v2.6.1/keda-2.6.1.yaml), we can produce a yaml with just CRDs next to it.

The release is being done here:

keda/.github/workflows/release-build.yml

Lines 57 to 60 in 8c85751

	- name: Release Deployment YAML file
	run: make release
	env:
	VERSION: ${{ steps.get_version.outputs.VERSION }}

@ishioni are you willing to contribute this?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[dmendres]

We have another use case. We'd like conditional deployment of the KEDA resources from a template (e.g. templates/keda.yaml) but Helm 3.x must process the CRDs in advance. We don't need conditional deployment of the CRDs.