mirror of
https://github.com/vacp2p/status-linea-besu.git
synced 2026-01-09 15:28:09 -05:00
K8 changelog (#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>
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user