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
Our ScaledJob CRD uses k8s.io/api/batch/v1/JobSpec which results in a CRD that is not possible to deploy on k8s 1.18:
kubectl apply -f deploy/crds/keda.sh_scaledjobs_crd.yaml ✔
The CustomResourceDefinition "scaledjobs.keda.sh" is invalid:
* spec.validation.openAPIV3Schema.properties[spec].properties[jobTargetRef].properties[template].properties[spec].properties[containers].items.properties[ports].items.properties[protocol].default: Required value: this property is in x-kubernetes-list-map-keys, so it must have a default or be a required property
* spec.validation.openAPIV3Schema.properties[spec].properties[jobTargetRef].properties[template].properties[spec].properties[initContainers].items.properties[ports].items.properties[protocol].default: Required value: this property is in x-kubernetes-list-map-keys, so it must have a default or be a required property
As a workaround we need to manually mark protocol property as reguired in the generated CRD (on a 3 places), after every CRD generation.
Could the patch file be merged in with the CRD? I am trying to deploy keda using Jsonnet and need a static location for the CRD to apply and I cannot use helm or kustomise.
Validation changes were introduced in k8s 1.18: https://kubernetes.io/docs/setup/release/notes/#other-api-changes
Our ScaledJob CRD uses
k8s.io/api/batch/v1/JobSpec
which results in a CRD that is not possible to deploy on k8s 1.18:As a workaround we need to manually mark
protocol
property asreguired
in the generated CRD (on a 3 places), after every CRD generation.We need to wait till this issue is solved: operator-framework/operator-sdk#3235
The text was updated successfully, but these errors were encountered: