diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9e18acb7a9..7e4ef2a6a3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,20 +11,29 @@ on `--privacy-onchain-groups-enabled`. [\#1222](https://github.com/hyperledger/b
 * In an IBFT2 network, a fixed block reward value and recipient address can be defined in genesis file [\#1132](https://github.com/hyperledger/besu/pull/1132)
 * JSON-RPC HTTP API Authorization: exit early when checking user permissions. [\#1144](https://github.com/hyperledger/besu/pull/1144)
 * HTTP/2 is enabled for JSON-RPC HTTP API over TLS. [\#1145](https://github.com/hyperledger/besu/pull/1145)
-* Color output in consoles. It can be disabled with `--color-enabled=false`
+* Color output in consoles. It can be disabled with `--color-enabled=false` [\#1257](https://github.com/hyperledger/besu/pull/1257)
 * Add compatibility with ClusterIP services for the Kubernetes Nat Manager  [\#1156](https://github.com/hyperledger/besu/pull/1156)
 * Add fee cap for transactions submitted via RPC. [\#1137](https://github.com/hyperledger/besu/pull/1137) 
 
 ### Bug fixes 
 
-* When the default sync mode was changed to fast sync for named networks,
-there was one caveat we didn't address. The `dev` network should've been full sync by default.
-This has now been fixed.
+* When the default sync mode was changed to fast sync for named networks, there was one caveat we didn't address. The `dev` network should've been full sync by default. This has now been fixed. [\#1257](https://github.com/hyperledger/besu/pull/1257)
 * Fix synchronization timeout issue when the blocks were too large [\#1149](https://github.com/hyperledger/besu/pull/1149)
 * Fix missing results from eth_getLogs request. [\#1154](https://github.com/hyperledger/besu/pull/1154)
+* Fix issue allowing Besu to be used for DDoS amplification. [\#1146](https://github.com/hyperledger/besu/pull/1146)
 
 ### Known Issues 
 
+Known issues are open issues categorized as [Very High or High impact](https://wiki.hyperledger.org/display/BESU/Defect+Prioritisation+Policy).
+
+#### Previously identified known issues
+ 
+- [Scope of logs query causing Besu to hang](KNOWN_ISSUES.md#scope-of-logs-query-causing-besu-to-hang)
+- [Eth/65 loses peers](KNOWN_ISSUES.md#eth65-loses-peers)
+- [Fast sync when running Besu on cloud providers](KNOWN_ISSUES.md#fast-sync-when-running-besu-on-cloud-providers)
+- [Privacy users with private transactions created using v1.3.4 or earlier](KNOWN_ISSUES.md#privacy-users-with-private-transactions-created-using-v134-or-earlier)
+- [Permissioning issues on Kubernetes](KNOWN_ISSUES.md#Kubernetes-permissioning-uses-Service-IPs-rather-than-pod-IPs-which-can-fail)
+- [Restarts caused by insufficient memory can cause inconsistent private state](KNOWN_ISSUES.md#Restart-caused-by-insufficient-memory-can-cause-inconsistent-private-state)
 
 ## 1.5 Breaking changes
 
diff --git a/KNOWN_ISSUES.md b/KNOWN_ISSUES.md
index 0ce09c165e..ad5794af70 100644
--- a/KNOWN_ISSUES.md
+++ b/KNOWN_ISSUES.md
@@ -46,3 +46,19 @@ A critical issue for privacy users with private transactions created using Hyper
 or earlier has been identified. If you have a network with private transaction created using v1.3.4 
 or earlier, please read the following and take the appropriate steps: 
 https://wiki.hyperledger.org/display/BESU/Critical+Issue+for+Privacy+Users 
+
+## Kubernetes permissioning uses Service IPs rather than pod IPs which can fail
+
+When using permissioning on Kubernetes, nodes don't join and start the network and chain as expected: they check permissions and allow the services. It appears that some of the socket connections use the pod IP which [causes Besu to halt](https://github.com/hyperledger/besu/issues/1190). 
+
+Workaround -> Do not use permissioning with Kubernetes. 
+
+A fix for this issue is being actively worked on. 
+
+## Restart caused by insufficient memory can cause inconsistent private state
+
+While running reorg testing on Besu and Orion, insufficient memory caused Besu to restart, resulting in the state on that machine to become inconsistent with the rest of the members of the privacy group. 
+
+Workaround -> Ensure you allocate enough memory for the Java Runtime Environment that the node does not run out of memory.
+
+A fix for this issue is being actively worked on.