When we merge in the cluster-aware clients from https://github.com/kcp-dev/kcp/issues/1943 , we're going to incur a huge refactoring cost. Furthermore, when any controller author attempts to migrate their single-cluster-context controller or program to kcp, they will incur the same cost. This can be done programatically and should be automated.
Proposed Solution
As an author of a pre-existing controller in a single-cluster-context
I want to migrate to using cluster-aware clients using a tool, without manual refactoring
So that my onboarding onto kcp is seamless and easy.
Feature Description
When we merge in the cluster-aware clients from https://github.com/kcp-dev/kcp/issues/1943 , we're going to incur a huge refactoring cost. Furthermore, when any controller author attempts to migrate their single-cluster-context controller or program to kcp, they will incur the same cost. This can be done programatically and should be automated.
Proposed Solution
As an author of a pre-existing controller in a single-cluster-context I want to migrate to using cluster-aware clients using a tool, without manual refactoring So that my onboarding onto kcp is seamless and easy.
Alternative Solutions
No response
Want to contribute?
Additional Context
No response