Skip to content

Verify the install path on Azure AKS (no code required) #103

Description

@MSKazemi

No code required. You need a Azure AKS cluster and about an hour.

CI runs every test on Kind only. Nobody has verified KubeIntellect on Azure AKS, so we genuinely do not know whether it works there — and ADOPTERS.md is honestly empty rather than padded.

Why this platform

The repo already targets Azure OpenAI, so AKS is the most likely real deployment pairing. Azure CNI and managed identity differ from Kind.

What to do

Follow the documented install path on a Azure AKS cluster and record what actually happens:

pip install kubeintellect
kubeintellect init            # setup wizard
kubeintellect serve           # API server on :8000

Then ask it something real about the cluster and try one read-only query end to end.

Report, as a comment on this issue:

  1. Platform + version — kubectl version, distro/managed flavour, node count
  2. Did the documented steps work verbatim? If not, the exact command and the exact error
  3. Any step the docs do not mention but that turned out to be required
  4. Whether RBAC behaved — a readonly key must be refused a mutating command before any approval prompt appears
  5. What you would change in the docs — even one sentence

Acceptance criteria

  • A comment covering the five points above, with real command output
  • Anything genuinely broken is filed as its own bug issue and linked here
  • If the docs need a change, a PR to v4/docs/ — or just say so and someone else can write it

A report saying "it did not work, here is exactly where it stopped" is more valuable than one saying it worked. That is the outcome we cannot get any other way.

⚠️ Redact before pasting — cluster output contains node names, namespaces and registries. And please use a non-production cluster, or a readonly key if it must be a real one.

Credit

This counts. You are named in the release notes exactly like a code contributor
(GOVERNANCE.md), and if you
add yourself to ADOPTERS.md
your environment becomes one of the ones we protect and keep backward-compatible.

(Note: a comment alone will not appear on GitHub's Contributors graph, which counts merged
commits. A one-line docs PR from what you find will — and is usually warranted.)

Task metadata

Difficulty Beginner
Estimated time ~1 hour
Skills Kubernetes operations. Access to a Azure AKS cluster. No Python, no code.
Mentor @MSKazemi — ask on this issue, or in Q&A
Status 🟢 Unclaimed — comment "I'd like to take this" and it will be assigned to you

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions