-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
clarify tested/supported versions of transitive or third-party dependencies #12328
Comments
/sig testing |
/assign @timothysc @luxas @roberthbailey |
Some initial thoughts: etcd I think of etcd as largely an implementation detail of the apiserver and owned by sig-apimachinery. I know that other folks in sig cluster lifecycle (e.g. @justinsb) have a different opinion, but I would love to see folks from apimachinery who work more closely with etcd (such as @jpbetz) help define the supported versions per release and the upgrade process. My understanding is that right now we basically test a single version of etcd3 for each release (at least for the vast majority of tests) although we still claim support for etcd2 as well. Dependencies These are generally integrated / tested / qualified by the SIG that owns the interface, e.g. sig node would qualify various CRIs for a release or sig storage would qualify the CSI driver for a release. From what I've seen historically, as with etcd it's often been a single implementation that gets the vast majority of the test cycles and then an alternate version may be run through some tests to ensure compatibility. Addons Right now "addons" are implicitly bundled with the release in the form of container version references in yaml files in the cluster directory of the release tarball. I'm not sure who, other than kube-up, actually relies on this, but as we would like to get rid of the cluster directory hopefully the list of consumers of those yaml files is small. @justinsb and @johnsonj have proposed a new way for managing addons, and along with that we will need to come up with a way to track addons per k8s release. One suggestion has been to use the bundle (https://github.com/GoogleCloudPlatform/k8s-cluster-bundle) as a schematic way to represent a set of components that have been tested and qualified together. |
/wg lts |
started a doc to organize work efforts related to kubernetes dependencies at https://docs.google.com/document/d/1WA8N7C48nkJmme9a96DU0o9jBpeycPhht8WF-Eam9QQ/edit?usp=sharing |
/language en |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@liggitt: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@liggitt: This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Follow up from #11060, tracked in #12329
what is our stated support or testing for transitive or third-party dependencies?
I see three main categories of dependencies and sets of questions that are unanswered in current documentation:
Finally, where should this information be maintained (a unified page with a version matrix, per-release, or something else)?
@kubernetes/sig-testing @kubernetes/sig-release @kubernetes/sig-cluster-lifecycle
(#12233 is open specifically for etcd)
Page to Update:
https://kubernetes.io/docs/setup/version-skew-policy/
The text was updated successfully, but these errors were encountered: