Description
Currently we are using a workaround in Solo to set a aarch JVM parameter that only works for M3 and M4 chips. I propose that instead we
-
upgrade the solo-containers to use JDK v21.0.7 which based on JDK-8345296 corrects the issue. DONE: use v0.37.2
-
add the zip and unzip install into the Dockerfile for
ubi8-init-java21
-
update the solo-charts to use the new version of the solo
ubi8-init-java21
-
update Solo to use the new chart
-
update Solo to remove the conditional check for aarch64
-
update Solo to remove the install of zip
-
update Solo to remote the uninstall of zip
-
have @Ivo-Yankov or @instamenta validate everything still works
-
update Solo
release/v0.35
to use the new Helm chart -
with Solo v0.35.2 do a
task default-with-relay
, then do ahelm upgrade XYZ
with this new latest version of Solo
Helm charts, validate that nothing gets killed or restarted and that the ledger, mirror node, explorer, and relay are still functional. This will provide an upgrade pathway for our production network when we implement the upgrade logic. -
required by: add doc warning for Apple M3/M4 chip bug #1883