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>

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 77929b7..b8e52fe 100644 (file)
--- 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