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

Move Taints and Tolerations to GA #60281

Closed
1 task done
bsalamat opened this issue Feb 23, 2018 · 3 comments
Closed
1 task done

Move Taints and Tolerations to GA #60281

bsalamat opened this issue Feb 23, 2018 · 3 comments
Assignees
@bsalamat
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Milestone
v1.10

Comments

@bsalamat
Copy link
Member

bsalamat commented Feb 23, 2018 •
edited
Loading

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature

Taints and tolerations is a beta feature in Kubernetes 1.9. We would like to move it to GA status in 1.10.
My initial investigations show that we only need to update the docs to mention that it is GA.

Task tracker:

  • Update kubernetes.io and remove notions of the feature being Beta.

/sig scheduling
/assign
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Feb 23, 2018
@bsalamat bsalamat mentioned this issue Feb 23, 2018
Merged
@bsalamat bsalamat added this to the v1.10 milestone Feb 23, 2018
@jdumars
Copy link
Member

jdumars commented Feb 23, 2018

Thank you for getting the docs in place for this. Could you go ahead and add "approved-for-milestone" label to it, as well priority and status? That will help it stay in the milestone.

@bsalamat bsalamat added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. approved-for-milestone labels Feb 23, 2018
@jberkus jberkus mentioned this issue Feb 23, 2018
Closed
@jberkus
Copy link

jberkus commented Feb 28, 2018

Increasing priority to critical-urgent since we are now in Code Freeze. Please update the issue regularly with status information.

/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Feb 28, 2018
@bsalamat
Copy link
Member Author

I think we can close it. Not much needed to be done other than updating the docs and docs are already updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bsalamat bsalamat

Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
v1.10
Development

No branches or pull requests
4 participants
@jberkus @jdumars @bsalamat @k8s-ci-robot