-
Story
-
Resolution: Done
-
Medium
-
None
Saw this on cnet yesterday - to fix
Katel34 raised is as well in DCAEGEN2-1018
https://github.com/kubernetes/kubernetes/issues/71411
https://www.zdnet.com/article/kubernetes-first-major-security-hole-discovered/
upgrade from 1.6.22 to 1.6.25 to move to kubernetes 1.11.3/1.11.5
Kubernetes 1.11.5 (server only) in Rancher 1.6.25 has the same fix as kubernetes 1.12.3 for https://github.com/kubernetes/kubernetes/issues/71411
https://github.com/rancher/rancher/releases/tag/v1.6.25
An upgrade from 2.9.1 of Helm has not been scoped yet
there are 4 other scripts - getting them
- is blocked by
-
LOG-806 upgrade rancher/kubernetes from 1.6.18/1.10 to 1.6.22|23/1.11 to align with INT-586 71375 29 Oct upgrade
- Closed
- relates to
-
LOG-353 Anti-Crypto: Security RBAC Lockdown of OOM Kubernetes until 1.10 upgrade - port 10249-10255 - specifically 10250 and 8880 oauth
- Closed
-
OOM-1299 SPIKE: Determine versions of Kubernetes and Helm to use in Casablanca
- Closed
-
OOM-1496 Update K8s and Helm for Dublin Release
- Closed
-
OOM-1499 Update Dublin OOM user guide with Helm/K8s versions
- Closed
-
OOM-1539 CVE-2018-1002105: proxy request handling in kube-apiserver can leave vulnerable TCP connections · Issue #71411 · kubernetes/kubernetes · GitHub
- Closed
-
OOM-1532 kubectl exec/log pod connection problems after x days - k8s 1.12 upgrade candidate
- Closed
-
TSC-25 Task Force to implement CD (Continuous Deployment)
- Closed
-
DOC-368 Rancher upgrade from 1.6.22 to 1.6.25 pushes kubernetes to 1.11.5
- Closed
-
TSC-75 CVE security governance of deployment undercloud (Docker, Kubernetes, Helm, Rancher) - propose new CLM job
- Closed
- mentioned in
-
Page Loading...