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
Keeping legacy CRD's adds support overhead (like #43). These legacy CRD's also do not support resource conversion so can only use the storage version for each CRD.
My suggestion would be maintain best-effort support until Kubernetes v1.21 is released upstream (~March 2021) and then deprecate these and move the require kubeVersion in the chart.yaml from v1.11 to v1.16.
The text was updated successfully, but these errors were encountered:
mcavoyk
added
the
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
label
Oct 21, 2020
Keeping legacy CRD's adds support overhead (like #43). These legacy CRD's also do not support resource conversion so can only use the storage version for each CRD.
My suggestion would be maintain best-effort support until Kubernetes v1.21 is released upstream (~March 2021) and then deprecate these and move the require kubeVersion in the chart.yaml from v1.11 to v1.16.
The text was updated successfully, but these errors were encountered: