Crane has transformation plugins concept, this allows provide patches for specific use-cases. Later, we might need update crane plugin system to support more powerful transformations including coverting between resource types and platform updates scenarios.
However for now, we need ensure defaut kubernetes plugin is up-to-date with our uses cases and current Kubernets and OpenShift 4 versions. Focusing only on resources cleanup, not update/changes scenarios.
Look on:
https://github.com/migtools/crane-lib/tree/main/transform/kubernetes
https://github.com/migtools/crane-plugin-openshift
And "orchestration" with:
https://github.com/migtools/crane/tree/main/cmd/plugin-manager
https://github.com/migtools/crane-plugins/tree/main
Identify&document gaps/leftovers etc. that need to be addressed and address those.
One small piece was migtools/crane-lib#137, but we need deeper check if plugins do their job right.
Crane has transformation plugins concept, this allows provide patches for specific use-cases. Later, we might need update crane plugin system to support more powerful transformations including coverting between resource types and platform updates scenarios.
However for now, we need ensure defaut kubernetes plugin is up-to-date with our uses cases and current Kubernets and OpenShift 4 versions. Focusing only on resources cleanup, not update/changes scenarios.
Look on:
https://github.com/migtools/crane-lib/tree/main/transform/kubernetes
https://github.com/migtools/crane-plugin-openshift
And "orchestration" with:
https://github.com/migtools/crane/tree/main/cmd/plugin-manager
https://github.com/migtools/crane-plugins/tree/main
Identify&document gaps/leftovers etc. that need to be addressed and address those.
One small piece was migtools/crane-lib#137, but we need deeper check if plugins do their job right.