K8 changelog (hyperledger#1339)

* Remove ROADMAP.md and link Wiki Roadmap in README.md

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Update changelog to add EIP 2315

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Update Changelog for 1.5

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Remove developper advocate contact

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

* Remove K8s issue from known issues

Signed-off-by: Tim Beiko <t.beiko23@gmail.com>

CHANGELOG.md

@@ -10,13 +10,14 @@
 
 ### Bug Fixes
 
+* K8S Permissioning to use of Service IP's rather than pod IP's which can fail [\#1190](https://github.com/hyperledger/besu/issues/1190)
+
 #### Previously identified known issues
 
 - [Logs queries missing results against chain head](KNOWN_ISSUES.md#Logs-queries-missing-results-against-chain-head)
 - [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)
 - [Changes not saved to database correctly causing inconsistent private states](KNOWN_ISSUES.md#Changes-not-saved-to-database-correctly-causing-inconsistent-private-states)
 
 ### Breaking Change to Onchain Privacy Group Management 

KNOWN_ISSUES.md

@@ -47,14 +47,6 @@ or earlier has been identified. If you have a network with private transaction c
 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. 
-
 ## Changes not saved to database correctly causing inconsistent private states
 
 While running reorg testing on Besu and Orion, inconsistent private states were observed in some long running tests