NDB Operator Release Notes  /  Changes in NDB Operator 8.0.35-1.0.4 (2023-10-25, General Availability)

Changes in NDB Operator 8.0.35-1.0.4 (2023-10-25, General Availability)

This is MySQL NDB Operator 8.0.35-1.0.4, a GA release of NDB Operator, a Kubernetes Operator for MySQL NDB Cluster.

For additional downloads and the source of MySQL NDB Operator visit https://dev.mysql.com/downloads/ndb-operator/ and https://github.com/mysql/mysql-ndb-operator.

For more information on MySQL NDB Operator see the online documentation at https://dev.mysql.com/doc/ndb-operator/en/.

For more information about MySQL NDB Cluster, see https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster.html.

Bugs Fixed

  • This fix addresses the following issues:

    1. The check_version() shell script function, responsible for checking the MySQL Cluster version and whether it meets the minimum required, contained errors.

    2. The Java SDK included in the Docker file mysql-cluster-builder:ol8 was updated to version 17.

    (Bug #35691446)

  • NDB Operator did not detect initiation script failures, causing it to start the mysqld container even when there were errors in the init container.

  • In a multi-node Kubernetes environment, an issue arose when the user opted to use an image secret to retrieve the NDB Operator image while deploying it, leading to a situation where one or more pods encounter failures due to image pull failures. This problem emerged because all NDB Cluster pods spawned by NDB Operator include an initialization container that necessitates the presence of the ndb-operator image.

    The root of the issue was that the necessary image pull secret was not included in the pod specifications. Consequently, when a pod was instantiated on any node other than the one where NDB Operator was deployed, it lacked the essential image pull secret, which meant that, since the required image could not be fetched from the repository, pod initialization could not take place.