Skip to content

[Automated] Draft docs (kagent): chore: remove unsupported Azure OpenAI inline token configuration - #731

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-kagent-3651
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-kagent-3651

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

kagent-dev/kagent#3651 — chore: remove unsupported Azure OpenAI inline token configuration

Docs versions: main

No code-path rule covers 1 touched file(s). The planner could route these only by identifier search, so the candidate pages may miss what they changed, including in the other mode:

  • go/core/pkg/env/providers.go

What changes for users: azureAdToken is no longer available on ModelConfig for Azure OpenAI. Users must use an API key Secret, token passthrough, or actorJwt credentials instead of setting an inline Microsoft Entra ID token.

What the docs now say: The Azure OpenAI provider page no longer lists azureAdToken as a provider setting or authentication option. Its authentication section now states that azureAdToken is not available in ModelConfig and points readers to the supported credential configurations.

How kagent-3651 was drafted

Plan, and what changed it

  • Planned: Remove the stale azureAdToken authentication option from the Azure OpenAI provider guide.
  • Learned: the code diff also removes generated API and Helm reference rows, and grep found stale generated rows plus the same prose in latest, but the work-list authorizes only main and generated references are covered by update-ref-docs.yaml.
  • Did: Updated docs-site/content/kagent/main/setup/model-providers/azure-openai.md.

Why a documentation change is necessary

The pull request removes azureAdToken from the ModelConfig Go type, the CRD schema, Helm values, the runtime translation path, and the UI provider optional parameters. The Azure OpenAI guide listed azureAdToken as a provider setting and as an authentication configuration, so a reader could try to configure a field that the current API no longer serves. The generated main/reference/api-ref.md and main/reference/helm.md pages still show stale rows in this checkout, but the work-list marks those pages as generated reference output.

How to verify this change

  1. Install the generated main kagent CRDs, then apply the Azure OpenAI ModelConfig from setup/model-providers/azure-openai.md. The API server accepts the resource.
  2. Add azureAdToken under spec.azureOpenAI in that ModelConfig, then run kubectl apply --dry-run=server --validate=strict -f <file>. The API server reports that spec.azureOpenAI.azureAdToken is unknown.
  3. Run kubectl explain modelconfig.spec.azureOpenAI.azureAdToken. The command reports that the field does not exist.

Proposed release note

No proposed-release-note.md: markers.notes_placeable is false for this repository. The dossier release-note text is: Remove azureAdToken from ModelConfig because the kagent runtime does not consume the emitted AZURE_AD_TOKEN value, and it bypasses v1's gateway credential injection approach.

Files in this pull request

  • docs-site/content/kagent/main/setup/model-providers/azure-openai.md
How the pages were chosen (triage report)

Feature clusters

Kept apart on purpose. Merging wrongly produces a guide that documents two things and explains neither, so these are reported for a person to merge rather than grouped automatically:

Draft a documentation change

kagent-dev/kagent#3651 — chore: remove unsupported Azure OpenAI inline token configuration

  • Product: kagent (upstream) → kagent-dev/website
  • Docs version: main
  • Summary (read from the body): Remove azureAdToken from ModelConfig because the Kagent runtime does not consume the emitted AZURE_AD_TOKEN value, and it bypasses v1's gateways credential injection approach.
  • Not tested: no cluster was available, so every command in this diff is unrun
  • No rule covers 1 touched file(s). The candidate pages below come from the files that DID match a rule, so they may scope this narrower than the change is. Read these before deciding the change is only about the pages listed:
    • go/core/pkg/env/providers.go

Draft branch: pr-tracker-draft-kagent-3651

…AI inline token configuration

Signed-off-by: GitHub Action <action@github.com>
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