-
Notifications
You must be signed in to change notification settings - Fork 73
Support kubectl config #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This would need extensive testing and updates to https://github.com/Flux159/mcp-server-kubernetes/blob/main/src/utils/kubernetes-manager.ts to support changing the kubectl config / contexts. I think some new changeContext function would need to reset everything that is set in the constructor, then expose that to the llm via a tool. There's also probably some nuance around what state we're tracking in kubernetes-manager - if we want to properly clear things across multiple contexts. Most tools use k8sManager.getCoreApi, etc. and we would need to make sure that those work correctly after a config or context change. You may also face this issue, but as long as it's documented that config changes will not work with the same username due to a caching issue in the client dependency that should be fine. |
As mentioned in #97 (comment) - there may be an api that supports this in the javascript client which would make it a bit easier to implement. |
We now have list contexts, set context, and get context tool calls in Note that we're not supporting every kube config operation - @jxs1211 are there other operations than the ones I listed that you want to add or should this be closed? |
I want to propose a feature for supporting kubectl config operations and would like to contribute the feature.
The text was updated successfully, but these errors were encountered: