Context

KCP used to maintain their own fork of the controller-runtime with adjustments tailored to work with the kcp ecosystem. There is a new kubernetes SIG evolving around the concept of providing a multicluster-runtime. KCP has already written a Provider for this new project and stopped maintaining their fork. So we need to migrate our existing controllers and their logic to work with the new multicluster-runtime.

Links:

• Main mc Repo: https://github.com/kubernetes-sigs/multicluster-runtime
• Example on usage with APIExports in KCP: https://github.com/kcp-dev/multicluster-provider/tree/main/examples/apiexport

Tasks

• Provide Wrappers for methods in the lifecycle package that work with the new multicluster-runtime interfaces for:

  • Managers
  • Controllers
  • Reconcile function

• Provide means of exposing and using the GetCluster manager methods into the subroutines

• Use the right builder patterns available with the new runtime

• make sure to properly embrace the ability to customize providers while doing this

• The existing methods should still work for standard kubernetes controllers - investigate the best way to maximize reuse between the two runtime but still allow for the usage of the full potential between the two runtimes

• [ ]