Instead of deploying CRDs using kubectl, deploy them as part of helm subchart.

[amannijhawan]

When CRDs are installed directly with kubectl, it complicates the process for users integrating Helm into broader CI/CD pipelines, like ArgoCD. This issue arises because ArgoCD cannot execute commands that fall outside the scope of Helm templates.

Keeping CRDs separate from Helm charts doesn't align well with such workflows.

A better strategy is to include CRDs within a Helm subchart, which streamlines the process.

Ref: https://yugabyte-db.slack.com/archives/CG0KQF0GG/p1713979320920149?thread_ts=1713971568.948539&cid=CG0KQF0GG