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
If I try to create or update a TPC with a non existing minor version of kubernetes, the CRD API call succede but the tcp remain in an provisioning state.
Unfortunately, the single way to address this is to hard-code all the available versions of Kubernetes.
This would require more maintenance toil, and it could a technical debt in the future where we could specify a different image repository mirror or any different Kubernetes distribution (although not yet supported).
We technically could check in an admission webhook, if there are images for the given Kubernetes version (or given image for custom Kubernetes distros), but I do not see the value, tbh. CP will spawn and give you an ErrImgPull error, which is simple and clear.
CP will spawn and give you an ErrImgPull error, which is simple and clear.
It could be anything else - like ghcr is not available, the image was removed etc. I think that the precise error message on admission webhook side would be much cleaner and more understandable. Unfortunately, it means, that the list of supported k8s versions should be hardcoded somewhere in the code of operator, but maybe it is good thing (particularly for promotion of commercial version of kamaji)...
If I try to create or update a TPC with a non existing minor version of kubernetes, the CRD API call succede but the tcp remain in an provisioning state.
How to reproduce:
Expected behavior
Get an error similar to the one obtained with a non existing major version
admission webhook "vtenantcontrolplane.kb.io" denied the request: unable to upgrade to a version greater than the supported one, actually 1.26.0
The text was updated successfully, but these errors were encountered: