-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Taints/tolerations #108
Comments
We will be moving this feature to beta in 1.6. Tracking issue is |
@davidopp could you please update the documentation status of the feature. |
This has been moved to beta, still needs documentation. |
In addition to documentation, we need to update the rescheduler and cluster autoscaler to use the beta fields instead of alpha annotations. I've filed issues for this: |
These aren't guaranteed to be at the same version as the cluster's master,
right? So you need to support both for a while.
…On Wed, Mar 1, 2017 at 11:41 PM, David Oppenheimer ***@***.*** > wrote:
In addition to documentation, we need to update the rescheduler and
cluster autoscaler to use the beta fields instead of alpha annotations.
I've filed issues for this:
kubernetes-retired/contrib#2381
<kubernetes-retired/contrib#2381>
kubernetes-retired/contrib#2382
<kubernetes-retired/contrib#2382>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#108 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHuudopYSH4A-zwQzrhTw9nAOjSrzB4vks5rhnK0gaJpZM4KLtdy>
.
|
Most deployment platforms will upgrade all the master components at approximately the same time, so it just needs to not do anything bad during the short window when the versions mismatch. But we're also going to have instructions on what order to upgrade the components if they don't upgrade at approximately the same time (in particular, upgrade the rescheduler first). @piosz is working on all of this. |
@davidopp any update on this feature? Docs and release notes are required (please, provide them to the features spreadsheet. |
Speadsheet updated. Docs not done yet. |
Documentation PR out for review: kubernetes/website#2774 |
@aveshagarwal noted that in addition to the above doc PR, we also need the following doc updates:
|
Oh, and also, I have text for the "Notable Changes to Existing Behavior" and "Action Required Before Upgrading" sections of the Release Notes ready to go, but won't be able to create a PR for that until https://github.com/kubernetes/features/blob/master/release-1.6/release-notes-draft.md is created. (BTW I'd like to change "Action Required Before Upgrading" to "Action Required Before or After Upgrading" for this release, since the scheduler features we moved from alpha to beta require using fields that only exist after you upgrade. So the action is actually taken after upgrade, not before.) |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
LOG-545: Cluster logging Elasticsearch rollover data design
* update dry-run feature yaml * update * fix
Description
Design doc discussion in kubernetes/kubernetes#18263, checked in here.
Implementation in kubernetes/kubernetes#24134
This feature first appeared in Kubernetes 1.4. I'm filing the issue to track moving it to Beta in 1.5 (kubernetes/kubernetes#25320).
See also #61
Progress Tracker
/pkg/apis/...
)@kubernetes/api
@kubernetes/docs
on docs PR@kubernetes/feature-reviewers
on this issue to get approval before checking this off@kubernetes/docs
on docs PR@kubernetes/feature-reviewers
on this issue to get approval before checking this off@kubernetes/api
@kubernetes/feature-reviewers
on this issue to get approval before checking this off@kubernetes/docs
@kubernetes/feature-reviewers
on this issue to get approval before checking this offFEATURE_STATUS is used for feature tracking and to be updated by
@kubernetes/feature-reviewers
.FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design
@kubernetes/feature-reviewers
member, you can check this checkbox, and the reviewer will apply the "design-complete" label.Coding
and sometimes http://github.com/kubernetes/contrib, or other repos.
@kubernetes/feature-reviewers
and they willcheck that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing. They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.
Docs
@kubernetes/docs
.The text was updated successfully, but these errors were encountered: