Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x-kubernetes-map-type: Invalid value "null" #757

Closed
sxd opened this issue Jan 2, 2023 · 3 comments
Closed

x-kubernetes-map-type: Invalid value "null" #757

sxd opened this issue Jan 2, 2023 · 3 comments

Comments

@sxd
Copy link

sxd commented Jan 2, 2023

While upgrade to the new versions of controller-tools and controller-runtime in CloudNativePG we hit this error while deploying the generated CRD into KinD 1.26.0:

CustomResourceDefinition.apiextensions.k8s.io "clusters.postgresql.cnpg.io" is invalid: [spec.validation.openAPIV3Schema.properties[spec].properties[walStorage].properties[pvcTemplate].properties[resources].properties[claims].items.x-kubernetes-map-type: Invalid value: "null": must be atomic as item of a list with x-kubernetes-list-type=set, spec.validation.openAPIV3Schema.properties[spec].properties[storage].properties[pvcTemplate].properties[resources].properties[claims].items.x-kubernetes-map-type: Invalid value: "null": must be atomic as item of a list with x-kubernetes-list-type=set, spec.validation.openAPIV3Schema.properties[spec].properties[resources].properties[claims].items.x-kubernetes-map-type: Invalid value: "null": must be atomic as item of a list with x-kubernetes-list-type=set]

We also hit the previous error #752 but this doesn't looks like it will match that error in specific and the patch doesn't seem to handled a null value at all

Regards,

@sxd
Copy link
Author

sxd commented Jan 3, 2023

This was a bug using version 0.9.2, with version 0.11.0 works but with version 0.11.1 which has only the revert of #752

@JoelSpeed
Copy link
Contributor

Your API type includes the corev1.ResourceRequirements struct which is currently broken in the K8s 1.26.0 release. The PR to fix it is kubernetes/kubernetes#114617 and that will be included in v1.26.1, whenever that is being cut.

@sxd
Copy link
Author

sxd commented Jan 3, 2023

@JoelSpeed thank for your answer! I'll close this ticket then doesn't make sense at all, thanks for your reply!

@sxd sxd closed this as completed Jan 3, 2023
BlaineEXE added a commit to BlaineEXE/rook that referenced this issue Feb 22, 2023
K8s v1.26.0 has a bug discussed here that causes failures in CI:
kubernetes-sigs/controller-tools#757

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
BlaineEXE added a commit to BlaineEXE/rook that referenced this issue Feb 22, 2023
K8s v1.26.0 has a bug discussed here that causes failures in CI:
kubernetes-sigs/controller-tools#757

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
BlaineEXE added a commit to BlaineEXE/rook that referenced this issue Feb 23, 2023
K8s v1.26.0 has a bug discussed here that causes failures in CI:
kubernetes-sigs/controller-tools#757

Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants