New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conformance profiles summary and motivation #1619
Conformance profiles summary and motivation #1619
Conversation
/assign @hh @Jefftree @smarterclayton |
This is a start on the profiles KEP, still a WIP of course. |
/hold |
65dce4a
to
daf8370
Compare
I think this gets us to our initial stages. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hh, johnbelamaric The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
||
- Should be able to define which tests to run up-front (eg: conformance, plus | ||
profiles, profiles only, etc) | ||
- May be able to detect or enumerate list of eligible profiles for a given |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this via some query-able endpoint under discussion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea of polling for features would be great.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't ironed out the technical details yet, but this is a great suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two questions but otherwise looks good
behavior definitions. | ||
* Design and implement a mechanism to validate whether a cluster conforms to | ||
each profile. | ||
* Document guidance on how to choose the scope of individual profiles. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and restrict the total number of profiles?
|
||
As a developer of an optional feature, I must be able to define behaviors for | ||
that feature that a vendor claiming support for the feature must follow. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whose responsibility is it to assign optional features to Profiles / create new Profiles?
I feel like as a developer I need to know this information if I want my feature to be included in Conformance testing.
OTOH, maybe inclusion in a Profile is up to someone else to decide
like you have a storage driver, etc) | ||
- Need to be able to selectively schedule Profile tests to nodes that support | ||
them (eg: Windows to windows nodes, GPU to nodes that have gpus, etc.) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm assuming roles related to certification are going to be done as a followup
/hold cancel |
No description provided.