docs: align site and proposals with v1alpha1 API#282
Open
HarshithaMS005 wants to merge 1 commit into
Open
Conversation
Update introduction, quickstarts, and proposal docs to reflect the implemented XAccessPolicy v1alpha1 shape (action, Inline/mcp.methods, spec-level ExternalAuth). Add site API reference and fix broken Reference nav. Signed-off-by: Harshitha MS <harshitha.ms@ibm.com>
k8s-ci-robot
added
the
kind/documentation
✅ Deploy Preview for kube-agentic-networking ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: HarshithaMS005 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
k8s-ci-robot
added
cncf-cla: yes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This PR aligns user-facing documentation with the implemented API: correct resource names and versions, the spec.action + authorization.type: Inline / mcp.methods model, and spec-level ExternalAuth. It adds a site API reference page (fixing the broken Reference nav) and adds implementation-status notes on design proposals so historical docs are clearly distinguished from what ships today.
Which issue(s) this PR fixes:
Fixes #274
Does this PR introduce a user-facing change?: