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.

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

Fix some links in CHANGELOG #44185

Merged
merged 1 commit into from
Apr 13, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
- [Downloads for v1.6.0](#downloads-for-v160)
- [Client Binaries](#client-binaries-2)
- [Server Binaries](#server-binaries-2)
- [WARNING: etcd backup strongly recommended](#warning:-etcd-backup-strongly-recommended)
- [WARNING: etcd backup strongly recommended](#warning-etcd-backup-strongly-recommended)
- [Major updates and release themes](#major-updates-and-release-themes)
- [Action Required](#action-required)
- [Certificates API](#certificates-api)
Expand Down Expand Up @@ -877,7 +877,7 @@ Features for this release were tracked via the use of the [kubernetes/features](
* Cluster Autoscaler respects Pod Disruption Budgets when removing a node.

### DaemonSet
* **[beta]** Introduce the rolling update feature for DaemonSet. See [Performing a Rolling Update on a DaemonSet](https://deploy-preview-2878--kubernetes-io-master-staging.netlify.com/docs/tasks/manage-daemon/update-daemon-set/).
* **[beta]** Introduce the rolling update feature for DaemonSet. See [Performing a Rolling Update on a DaemonSet](https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/).

### Deployment
* **[beta]** Deployments that cannot make progress in rolling out the newest version will now indicate via the API they are blocked ([docs](https://kubernetes.io/docs/user-guide/deployments/#deployment-status))
Expand Down