Skip to content

Conversation

Cali0707
Copy link

@Cali0707 Cali0707 commented Sep 26, 2025

This PR builds on the approach taken in #325, but makes it more generic so that we can configure how clients select the cluster based on the cluster provider strategy (currently supporting in-cluster and kubeconfig).

There is a contexts_list tool added as well, which is conditionally enabled when there are more than 15 contexts in the kubeconfig, as that is when we switch from using an enum parameter to a general string parameter.

@Cali0707
Copy link
Author

So far, this PR only adds the ClusterProvider interface and the implementation for a kubeconfig provider.

The idea is that the provider can be used to get a Manager instance for the cluster requested in the tool provider.

Barring any feedback against this approach, I will continue with adding the cluster parameter to tools whenever the number of clusters is > 1, and using the provider interface to get the correct manager to each tool.

@Cali0707

This comment was marked as resolved.

@Cali0707 Cali0707 marked this pull request as ready for review October 1, 2025 18:17
@Cali0707 Cali0707 changed the title [WIP] Multi Cluster Support feat: Multi Cluster Support Oct 1, 2025
@Cali0707
Copy link
Author

Cali0707 commented Oct 1, 2025

@manusa I tried to keep the changes separated out by commit to make reviewing easier, let me know if I should squash them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant