K8SSAND-1495 ⁃ Investigate JDK update issues with nodetool

[emerkle826]

Background

Recent JDK/JRE changes (both Java 8 and Java 11) have caused an issue with nodetool in Cassandra (see CASSANDRA-17581 for details). The fix should be in Cassandra versions 3.11.13 and 4.0.4.

Current situation

Management API images are based off DockerHub Cassandra images (we build images for Cassandra 3.11.7, 3.11.8, 3.11.11, 3.11.12, 4.0.0, 4.0.1 and 4.0.3). When changes go into Management API, we rebuild the images, pulling from those DockerHub base Cassandra images. The latest release of Management API is v0.1.37.

Dockerhub impact

As of May 5, 2022, Cassandra 3.11.12 and 4.0.3 images pull in the updated JRE, which causes the nodetool issue reported in CASSANDRA-17581 (see this DockerHub issue for details there). This means any Management API images based on those Cassandra versions we build after May 5 will pull the broken Cassandra images as a base, and will have the bug.

Investigate

Going forward, we may need to provide a workaround in our Cassandra 3.11.12 and 4.0.3 based images, or stop building new Management API images based on C* 3.11.12 and 4.0.3 (similar to what we did when we stopped making C* 3.11.9 and 3.11.10 based images due to an sstables corruption bug).

┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1495
┆priority: Medium

[emerkle826]

This was addressed with #196