1

I'm having the following issue installing Valero via the Velero CLI to and AWS Kubernetes cluster.

velero install \
     --provider aws \
     --bucket $BUCKET \
     --secret-file ./credentials-velero \    --use-restic --wait \
     --plugins velero/velero-plugin-for-aws:v1.0.0

The install fails, with the result:

An error occurred:

Error installing Velero. Use `kubectl logs deploy/velero -n velero` to check the deploy logs: Error creating resource CustomResourceDefinition/backups.velero.io: CustomResourceDefinition.apiextensions.k8s.io "backups.velero.io" is invalid: [spec.validation.openAPIV3Schema.properties[spec].properties[labelSelector].properties[matchLabels].additionalProperties: Forbidden: additionalProperties cannot be set to false, spec.validation.openAPIV3Schema.properties[spec].properties[hooks].properties[resources].items.properties[labelSelector].properties[matchLabels].additionalProperties: Forbidden: additionalProperties cannot be set to false]--

The only references to additionalProperties are nested deep in generated .yaml files, in this case the one for backups. I have no idea how this string value is being illegally set to false, but it's not a result of the flags I'm using as far as I can tell.

codeblue0000ff
  • 225
  • 3
  • 9
  • Check if you have any spaces or tabs after `\\`. This sometimes makes bash behave strangely. – Marcin Mar 03 '20 at 21:54
  • A [known issue](https://github.com/vmware-tanzu/velero/issues/2207) that was marked as a dupe of [the much chattier issue](https://github.com/vmware-tanzu/velero/issues/2159) – mdaniel Mar 04 '20 at 05:17

1 Answers1

0

Solution: I was trying to install Velero v1.2.0 on a Kubernetes v1.10 cluster (that I cannot upgrade at the moment). It turns out the two are incompatible. By downgrading to Velero v1.1.0, I was able to successfully install, and this error message disappeared.

codeblue0000ff
  • 225
  • 3
  • 9