WIP: ai-assistant: installation UI for AKS agent, similar to managed namespaces
- Dominant language
- TypeScript
- Stars
- 102
- Forks
- 25
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 22
Description
- installation UI for AKS agent (1)
- the UI is to do `az aks agent-init --resource-group --name `
- enable for this cluster
- X disable for this cluster
- Already has a UI for managed namespace, maybe do something like it.
- configure langchain to use aks agent mcp server
- aks agent config would be default for aks desktop
- multiple aks agents (one for each cluster)
- aks agent gets LLM keys from AI assistant configuration
- mcp configuration for aks agent mcp gets some environment variables (or flags) to get the LLM key.
- X OIDC maybe (langchain supports it) ??
- needed for AI assistant
- for AKS agent MCP
Contributor guide
Research direction
No files or tests are named. Start by reviewing the existing managed namespace UI and the `az aks agent-init` command, then trace how AKS Desktop configures the AI assistant and MCP servers. Done requires a defined installation UI, per-cluster enable/disable behavior, multiple-agent configuration, and a decision on how LLM keys are supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, typescript
- Domain
- ai, cloud, desktop, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100