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
When it comes to newtowking Korifi has two important dependencies - contour as an ingress implementation and gateway-api as an ingress api. There was a recent bump to contour v1.30.0, in which Contour updates its own dependency to the gateway-api to v1.1.0, which contains a breaking change. Accoding to the docs the user needs to delete the v1alpha2 and/or older versions of the BackendTLSPolicy CRD before installing the new version.
Action to take
In our next release we should document this bump as a breaking change pointing the users to the migration docs of the gateway-api. Korifi is gererall unaffected by this since it does not make uese of the BackendTLSPolicy CRD at all, but we should warn our users to use caution since deleting a custom resource definition will delete all its instances which may affect non-Korifi cluster configurations they might have
The text was updated successfully, but these errors were encountered:
Background
When it comes to newtowking Korifi has two important dependencies -
contour
as an ingress implementation andgateway-api
as an ingress api. There was a recent bump to contourv1.30.0
, in which Contour updates its own dependency to the gateway-api tov1.1.0
, which contains a breaking change. Accoding to the docs the user needs to delete thev1alpha2
and/or older versions of theBackendTLSPolicy
CRD before installing the new version.Action to take
In our next release we should document this bump as a breaking change pointing the users to the migration docs of the gateway-api. Korifi is gererall unaffected by this since it does not make uese of the
BackendTLSPolicy
CRD at all, but we should warn our users to use caution since deleting a custom resource definition will delete all its instances which may affect non-Korifi cluster configurations they might haveThe text was updated successfully, but these errors were encountered: