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
The kubernetes migration library framework is designed to be general. However currently it only defines migrations for Kubernetes related plugins.
The library can be generalized if we add plugin migration definitions for other plugins. This would be mostly a clerical task - albeit a sizable one.
If more plugins are supported, we could move the tool to its own repo.
Moving the tool to its own repo may even make sense now, as is with only k8s related plugin support, since its intended to be used as a library - it could be more cleanly cloned without cloning everything else in the deployment repo.
The kubernetes migration library framework is designed to be general. However currently it only defines migrations for Kubernetes related plugins.
The library can be generalized if we add plugin migration definitions for other plugins. This would be mostly a clerical task - albeit a sizable one.
If more plugins are supported, we could move the tool to its own repo.
Moving the tool to its own repo may even make sense now, as is with only k8s related plugin support, since its intended to be used as a library - it could be more cleanly cloned without cloning everything else in the deployment repo.
Related: #170
The text was updated successfully, but these errors were encountered: