Skip to content

Update guidance for layered product seeking conformance#95

Merged
ritazh merged 3 commits into
cncf:mainfrom
ritazh:update-layeredproduct-guidance
May 19, 2026
Merged

Update guidance for layered product seeking conformance#95
ritazh merged 3 commits into
cncf:mainfrom
ritazh:update-layeredproduct-guidance

Conversation

@ritazh

@ritazh ritazh commented Apr 23, 2026

Copy link
Copy Markdown
Collaborator

Addendum to #89 since the AI conformance leads and the community have not yet had a chance to review and comment.

Given that this may affect how the community interprets eligibility and certification scope for layered products, this topic would benefit from being discussed in a community call. If you have input, please comment in this PR or join the next AI Conformance project meetings

Revert "Add FAQ about certifying products on existing distributions"
@ritazh ritazh force-pushed the update-layeredproduct-guidance branch from d765d4d to 1550fa8 Compare April 23, 2026 02:29
@ritazh

ritazh commented Apr 23, 2026

Copy link
Copy Markdown
Collaborator Author

/hold

@jeefy :)

@ritazh

ritazh commented Apr 23, 2026

Copy link
Copy Markdown
Collaborator Author

Question: how many of the AI Conformance requirements need to be met by the layered product on top vs the underlying platform?

Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated
@ritazh

ritazh commented May 3, 2026

Copy link
Copy Markdown
Collaborator Author

@janetkuo @puja108 updated. PTAL

Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated

@puja108 puja108 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just minor comments for clarity, otherwise LGTM

Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated
Comment thread faq.md Outdated

@yuanchen8911 yuanchen8911 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Terminology. Three places say Kubernetes Conformance where the logic needs Kubernetes AI Conformance. Please apply @janetkuo's three suggestions.

  2. The "uniquely provide at least one feature" clause. As written it forces a MUST-level replacement, which pushes toward fragmentation and breaks layered products spanning multiple bases. @puja108's "at least in one place it must be different" is the right intent — please reword so the differentiator can be a SHOULD addition, a variant, or a roadmap feature.

Non-blocking: the MUST-leve typo, the missing "SHOULD already met by base" pattern, examples that do not name what is being replaced, and the NOTE callout being stylistically inconsistent with the rest of faq.md.

Meta: given this is normative guidance with real submission impact (PR #79 is waiting on it) and the PR description calls for community-call discussion.

Signed-off-by: Rita Zhang <[email protected]>
@ritazh

ritazh commented May 18, 2026

Copy link
Copy Markdown
Collaborator Author

Incorporated everyone's feedback. PTAL

@puja108 puja108 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@janetkuo janetkuo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This lgtm, thanks!

@ritazh ritazh merged commit 34233e9 into cncf:main May 19, 2026
1 check passed
@ritazh ritazh deleted the update-layeredproduct-guidance branch May 19, 2026 23:54
yuanchen8911 added a commit to yuanchen8911/k8s-ai-conformance that referenced this pull request May 20, 2026
NVIDIA NIM on EKS is a layered AI inference product on top of Amazon
EKS. This submission follows the layered-product guidance merged in
PR cncf#95: it records per-requirement layer ownership and identifies the
layered runtime's unique contributions (KAI Scheduler for gang
scheduling, kgateway with inference extension CRDs for inference
gateway, NIM Operator for AI-inference robust controller, NIM service
metrics).

All 9 MUST requirements are evidenced on the layered cluster; 3 SHOULD
requirements are implemented via the NVIDIA GPU Operator. Evidence is
hosted at:
https://github.com/NVIDIA/aicr/tree/main/docs/conformance/cncf/v1.35/nim-eks/evidence

Signed-off-by: Yuan Chen <[email protected]>
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.

5 participants