Vaults CRD fails schema validation

[sl1pm4t]

Bugs should be filed for issues encountered whilst operating bank-vaults.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:

When we use kubeconform to validate manifests generated by the vaults-operator helm chart, it fails on the vaults CRD with:

`CustomResourceDefinition vaults.vault.banzaicloud.com is invalid: For field metadata.creationTimestamp: Invalid type. Expected: string, given: null`

This is because the helm template has this:
https://github.com/banzaicloud/bank-vaults/blob/main/charts/vault-operator/crds/crd.yaml#L8

Expected behaviour:

It is expected the helm templates do not fail schema validation

Steps to reproduce the bug:
Run helm template against the vault-operator chart to generate the manifests.
Validate those manifests with kubeconform.

Additional context:
Add any other context about the problem here.

Environment details:

• Kubernetes version = 1.21.0
• Cloud-provider/provisioner = EKS
• bank-vaults version 1.15.8
• Install method: helm template + argocd

/kind bug

[github-actions]

Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.

[github-actions]

This issue has been marked stale for 20 days, and is now closed due to inactivity. If the issue is still relevant, please re-open this issue or file a new one. Thank you!