Skip to content

Update guidance for layered product seeking conformance#91

Merged
jeefy merged 1 commit into
cncf:mainfrom
ritazh:update-product-guidance
Apr 21, 2026
Merged

Update guidance for layered product seeking conformance#91
jeefy merged 1 commit into
cncf:mainfrom
ritazh:update-product-guidance

Conversation

@ritazh

@ritazh ritazh commented Apr 15, 2026

Copy link
Copy Markdown
Collaborator

Addendum to #89 since the AI conformance leads and the community has 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

@ritazh

ritazh commented Apr 15, 2026

Copy link
Copy Markdown
Collaborator Author

Comment thread faq.md
Comment thread faq.md

When submitting your application, you should refer to the third-party distribution's official conformance results to satisfy the base requirements.

**Important:** Building on a conformant distribution does not automatically make the layered product AI conformant. The layered product must independently demonstrate conformance for its own supported configuration.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Seems like the line above should be replaced by this line? Or at least the line above should be reworded.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It reads okay to me? "If you're building on 3rd party, refer to their k8s conformance results. PS that doesn't mean this is ai conformant"

@BenTheElder BenTheElder Apr 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

It isn't obvious that there's a limit to the k8s-conformance results of an underlying k8s distro versus more generally re-using conformance results from a product/installer/... when building on top.

Even then, I don't think you should do that for k8s results either. K8s conformance is for a specific product / installer and specific configuration.

So if for example they built their AI conformance solution on GKE, but they enabled GKE autopilot instead of a standard cluster, that configuration doesn't match the (k8s) conformant GKE configuration (and would fail some tests if you ran them instead of pointing to the documented GKE results).

Which is why I think you should just submit full results for the AI conformance configuration you are submitting.

@jeefy jeefy merged commit c1b7393 into cncf:main Apr 21, 2026
1 check passed
@terrytangyuan

Copy link
Copy Markdown
Member

@ritazh

ritazh commented Apr 22, 2026

Copy link
Copy Markdown
Collaborator Author

This PR should not have been merged without community input and leads review/approval. xpost: #79 (comment)

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.

4 participants