This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 276
SMI conversion webhook to upgrade to newer SMI API versions #2737
Labels
Milestone
Comments
shashankram
added
improvement / feature request
area/SMI
SMI implementation related
area/upgrade
Upgrade related
labels
Mar 4, 2021
michelleN
added
priority/P1
P1 priority
priority/P0
P0 priority
and removed
priority/P1
P1 priority
priority/P0
P0 priority
labels
Mar 9, 2021
This issue could be resolved via investigate smi-controller-sdk for osm project #3063 |
With issue #3396 we have decided to go with the option of : Implementing the SMI conversion webhook in OSM. All the necessary code to manage CRD updates, adding a conversion webhook to each of the SMI CRD's is now in OSM. The business logic to convert an SMI CRD from one version to another is CRD specific and will be added when we update the SMI CRD's in OSM. |
Closing issue for now as all the necessary code to support a conversion webhook for CRDs in OSM has been added |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Please describe the Improvement and/or Feature Request
Currently OSM does not support backward compatibility with SMI CRDs released in previous versions. This results in breaking changes when the SMI CRDs are upgraded and existing deployments that are leveraging a previous version of the custom resources (TrafficTargets, Splits, HTTPRouteGroups, TCPRoutes) can no longer function with a newer version of osm-controller that only supports the newer SMI API versions.
To mitigate this issue during upgrades, OSM must use a conversion webhook to convert older SMI resource versions to newer ones, and gradually migrate the deployments to use the newer versions before deprecating older ones in the cluster.
Since SMI does not provide a conversion webhook at this moment, we have the following options:
Conversion webhook ref: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/
Scope (please mark with X where applicable)
Possible use cases
Support gradual migration of older SMI versions in the cluster.
The text was updated successfully, but these errors were encountered: