[argo-rollouts] crd issue

[olfway]

Describe the bug
Currently, argo-rollouts helm chart uses its own crds, different from the ones in argo-rollouts repo

For example rollout-crd.yaml:
In helm chart it has "apiextensions.k8s.io/v1" and it seems field pruning is enabled, because spec.preserveUnknownFields is not defined

But some deployment fields are not declared in the rollout object, for example:

template.spec.containers:
  resources:
    type: object

Because of this, it's not possible to set requests and limits for a deployment, Kubernetes ignore and doesn't persist them

To Reproduce
Steps to reproduce the behavior:

1. Install argo-rollouts crd with helm chart
2. Create rollout object with requests or limits for pods
3. Get rollout object from k8s
4. See resources field is empty

Expected behavior
CRDs should contain all possible fields or have fields pruning disabled

Additional context
https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#field-pruning

Manifest from https://github.com/argoproj/argo-rollouts/blob/master/manifests/crds/rollout-crd.yaml has the same resources declaration but it is uses apiextensions.k8s.io/v1beta1

[github-actions]

Stale issue message