Repository navigation
|
We can't send cluster data to OpenAI or Azure. Can KubeIntellect run against a self-hosted or |
Replies: 1 comment
|
Partly today, and it is the most-requested item on the roadmap. What works now: the client is OpenAI-compatible, so pointing What is honestly missing: it is not a first-class, documented, tested path. There is no So: usable if you are willing to experiment, not something to depend on in production yet. Making it first-class is #17, and it
|
Partly today, and it is the most-requested item on the roadmap.
What works now: the client is OpenAI-compatible, so pointing
OPENAI_BASE_URLat anOpenAI-compatible server (Ollama, vLLM, LiteLLM, …) does function.
What is honestly missing: it is not a first-class, documented, tested path. There is no
CI coverage for a local backend, no guidance on which open models are good enough at the
tool-calling this system leans on heavily, and no tuned prompts for smaller models. The
coordinator delegates to subagents and relies on structured tool calls — weaker models degrade
in ways that matter for an incident-response tool.
So: usable if you are willing to experiment, not something to depend on …