kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixing english per PR review

This commit is contained in:
chrislovecnm 2017-10-10 12:20:19 -06:00
parent 97d0305fdf
commit 8792823ad9
1 changed files with 13 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/advisories/cve_2017_14491.md
View File

@ -7,15 +7,18 @@ with the full detail of the CVE. This exploit is not a Kubernetes specific vulne
## Current kops Status
`kop` release 1.7.1 addresses this CVE. This version of `kops` will upgrade and
create clusters. `kops` 1.8.x release does not contain the required changes.
`kops` release 1.7.1 addresses this CVE. This version of `kops` will upgrade and
create clusters. `kops` 1.8.0.alpha.1 release does not contain the required
changes, but when released 1.8.0.apha.2 will contain the required patches.
## Upgrading Cluster
To update a cluster. The kube-dns deployment will be automatically upgraded.
Replace `my-cluster.example.com` with the name of your cluster. If you are
upgrading a Kubernetes 1.4.x or 1.5.x cluster you may need to follow the
instruction below to create a required confimap for kube-dns.
The kube-dns deployment will be automatically upgraded when `kops update
cluster` is executed. Replace `my-cluster.example.com` with the name of your
cluster. If you are upgrading a Kubernetes 1.4.x or 1.5.x cluster you may need
to follow the instruction below to create a required confimap for kube-dns.
Upgrade command:
```bash
kops update cluster --yes --name my-cluster.example.com
@ -29,7 +32,7 @@ kubectl get deployment -n kube-system kube-dns \
```
The upgrade is will occur once the channels utilty picks up the change within a
few mintues.
few minutes.
## Tested Kubernetes Versions
@ -38,7 +41,7 @@ the new version of `kube-dns` deployment. Other versions should function, but
upgrading to tested version is recommended. We have had 1.4.x users upgrade
successfully, but we cannot validate full production stability. Local testing
in a non-production environment is always recommended. We are not able to
quatify the risk of using a non-tested version.
quantify the risk of using a non-tested version.
## Fixed kops releases
@ -162,4 +165,5 @@ _TODO_ if someone wants to provide the output.
## Thanks
Thanks to all that helped @mikesplain, @chrislovecnm, @snoby, @justinsb, @3h4x
Thanks to all that helped @mikesplain, @chrislovecnm, @snoby, @justinsb, @3h4x,
@aaronlevy