You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the below failure when trying to install CRDs in the argo-events helm chart.
kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (eventsources.argoproj.io):
error: resource eventsources.argoproj.io was not successfully created by the Kubernetes API server : CustomResourceDefinition.apiextensions.k8s.io "eventsources.argoproj.io" is invalid: spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required
kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (eventbus.argoproj.io):
error: resource eventbus.argoproj.io was not successfully created by the Kubernetes API server : CustomResourceDefinition.apiextensions.k8s.io "eventbus.argoproj.io" is invalid: spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required
kubernetes:apiextensions.k8s.io/v1:CustomResourceDefinition (sensors.argoproj.io):
error: resource sensors.argoproj.io was not successfully created by the Kubernetes API server : CustomResourceDefinition.apiextensions.k8s.io "sensors.argoproj.io" is invalid: spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required
To Reproduce
$ kubectl apply -f ./charts/argo-events/crds/sensor-crd.yml
The CustomResourceDefinition "sensors.argoproj.io" is invalid: spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required
Expected behavior
CRD should be created.
The text was updated successfully, but these errors were encountered:
The CustomResourceDefinition API type is promoted to apiextensions.k8s.io/v1 with the following changes:
- spec.versions[*].schema.openAPIV3Schema is now required when creating v1 CustomResourceDefinitions
Describe the bug
I get the below failure when trying to install CRDs in the argo-events helm chart.
To Reproduce
Expected behavior
CRD should be created.
The text was updated successfully, but these errors were encountered: