-
Notifications
You must be signed in to change notification settings - Fork 397
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
Add platforms documentation #1360
Conversation
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.
Thanks for adding this @saschagrunert! Left a few comments below, but mostly looks good to me. Let's allow some others to weigh in as well :)
/hold
release-engineering/platforms.md
Outdated
Tier 2 platforms are considered as "guaranteed to build". To achieve this, they | ||
have to fulfil the following criteria: | ||
|
||
- **Any** official binary release is provided for the platform. Building the |
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.
This is kind of tricky because we currently release artifacts that are not well tested or tested at all, but in the future it would be great if we "released" only Tier 1 artifacts, and published Tier 2 separately. However, I think we have to stick with that is defined here for now given our current state.
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.
@hasheddan do we track this open flanks already?
release-engineering/platforms.md
Outdated
- **All** official binary releases are provided for the platform. This includes | ||
container images as well as deb and rpm packages. Building the artifacts is | ||
integrated in the release process. |
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 am wondering if maybe support levels should be "per-binary". For instance if we thoroughly test kubectl
on darwin-amd64
it would technically still fall into Tier 2 by this definition.
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.
Alright, I changed the doc to outline that we can scope Tiers to single binaries. Let me know what you think.
528b7aa
to
96fe075
Compare
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.
@saschagrunert thanks for the update!
/lgtm
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 think as stated this document can give a reader a wrong impression of what is community support and the overall Kubernetes project's support stance, versus covering what it is that SIG Release does within that broader context. I've suggested a few slight changes in wording which soften what I think reads as overstatements around the term "support".
This adds the documentation about supported Kubernetes platforms to our repository. Signed-off-by: Sascha Grunert <sgrunert@suse.com>
96fe075
to
004bd6e
Compare
Makes sense, I changed the document as suggested. Please take a look again. |
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.
Re-adding my LGTM :) thanks again @saschagrunert!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, saschagrunert 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 |
I think we addressed most concerns and we can lift the hold. |
What type of PR is this:
/kind documentation
What this PR does / why we need it:
This adds the documentation about supported Kubernetes platforms to our
repository.
Which issue(s) this PR fixes:
Refers to #1337
Special notes for your reviewer:
None