summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorandreasgeissler <andreas-geissler@telekom.de>2018-11-29 14:45:24 +0000
committerandreasgeissler <andreas-geissler@telekom.de>2018-11-29 14:46:56 +0000
commitf92f643cccdf90ab3cc92c16e8ff89061e280a0a (patch)
treec91a91c1828d82fb0b59da055bea9a57ed3b7d20
parenta4007dd6135b3d2fe02d5ce7e88ded68155403cd (diff)
Update Known Issue
Updated the workaround and added links to k8s ticket and OOM issues related Issue-ID: OOM-1532 Change-Id: I43c1e23b1310dac4ae19d0b9c7fc07167da4f053 Signed-off-by: andreasgeissler <andreas-geissler@telekom.de>
-rw-r--r--docs/release-notes.rst7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 77929b7ff4..b8e52fe9d1 100644
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -42,10 +42,13 @@ Quick Links:
**Known Issues**
-Problem: kubectl connections to pods (kubectl exec|logs) will fail after a while due to a known bug in Kubernetes
+Problem: kubectl connections to pods (kubectl exec|logs) will fail after a while due to a known bug in Kubernetes (1.11.2)
Workaround: Restart of the kubelet daemons on the k8s hosts
-Fix: Will be delivered in the next release via a new Kubernetes version
+Fix: Will be delivered in the next release via a new Kubernetes version (1.12)
+- `K8S Bug Report <https://github.com/kubernetes/kubernetes/issues/67659>`_
- `OOM-1532 <https://jira.onap.org/browse/OOM-1532>`_
+- `OOM-1516 <https://jira.onap.org/browse/OOM-1516>`_
+- `OOM-1520 <https://jira.onap.org/browse/OOM-1520>`_
Version 2.0.0 Beijing Release