Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mark taints stable #1733

Closed
marquiz opened this issue Jun 6, 2024 · 5 comments
Closed

Mark taints stable #1733

marquiz opened this issue Jun 6, 2024 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone
v0.17

Comments

@marquiz
Copy link
Contributor

marquiz commented Jun 6, 2024

What would you like to be added:

Remove the experimental statements related to taints. Both in the docs and in the code.

Why is this needed:

Node tainting has been around since NFD v0.12. No bugs/issues have been reported (at least in a long while).
@marquiz marquiz added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 6, 2024
@marquiz
Copy link
Contributor Author

marquiz commented Jun 6, 2024

/milestone v0.17

@k8s-ci-robot k8s-ci-robot added this to the v0.17 milestone Jun 6, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 4, 2024
@k8s-triage-robot
Copy link

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:

  • 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:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2024
@marquiz
Copy link
Contributor Author

marquiz commented Oct 7, 2024

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Oct 7, 2024
@ArangoGutierrez ArangoGutierrez mentioned this issue Nov 4, 2024
Merged
@ArangoGutierrez
Copy link
Contributor

Done by #1944

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
v0.17
Development

No branches or pull requests
4 participants
@marquiz @ArangoGutierrez @k8s-ci-robot @k8s-triage-robot