search

kubernetes / node-problem-detector

This is a place for various problem detectors running on the Kubernetes nodes.
Apache License 2.0
2.94k stars 627 forks source link

Request for Inclusion of Compatibility Matrix in README.md #757

Open kirtanc25 opened 1 year ago

kirtanc25 commented 1 year ago

Issue Description: I would like to request the inclusion of a compatibility matrix in the README.md file of the node-problem-detector repository. The compatibility matrix would provide users with a clear overview of the Kubernetes versions supported by the tool.

A compatibility matrix is essential for users to quickly determine whether the node-problem-detector is compatible with their specific Kubernetes version, thus ensuring a smooth integration and usage experience.

An excellent example of a compatibility matrix can be found in the metrics-server repository's README.md file, specifically at this location: https://github.com/kubernetes-sigs/metrics-server#compatibility-matrix. This matrix serves as a useful reference for users to understand the supported Kubernetes versions by the metrics-server tool.

image

By including a compatibility matrix in the README.md file of the node-problem-detector repository, users would greatly benefit from the clear and concise information regarding the supported Kubernetes versions.

Thank you for considering this feature request. Please let me know if any additional information is required.

k8s-triage-robot commented 8 months ago

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

stephanosio commented 8 months ago

If providing a full compatibility matrix is deemed too time consuming, at least a brief mention of the minimum compatible Kubernetes version in the release notes would be very helpful.

k8s-triage-robot commented 7 months ago

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

wangzhen127 commented 6 months ago

To have a formal compatibility table, we will need additional qualification with the version combination. Currently we do not have that. In practice, NPD architecture is fairly stable already. More recent versions (v0.8.13+) should work with all supported kubernetes versions.

wangzhen127 commented 6 months ago

/remove-lifecycle rotten

k8s-triage-robot commented 3 months ago

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

k8s-triage-robot commented 2 months ago

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

k8s-triage-robot commented 1 month ago

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-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/node-problem-detector/issues/757#issuecomment-2325281574): >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: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
AnishShah commented 1 month ago

/reopen /remove-lifecycle rotten

k8s-ci-robot commented 1 month ago

@AnishShah: Reopened this issue.

In response to [this](https://github.com/kubernetes/node-problem-detector/issues/757#issuecomment-2327311165): >/reopen >/remove-lifecycle rotten > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.