Hi Folks, I finally found some time to continue working on running IoTDB in Kubernetes.
Some may remember that I posted a draft Helm Chart (https://artifacthub.io/packages/helm/apache-iotdb-single-node/apache-iotdb). Now I made some progress on running the Cluster Module in Kubernetes as well as the single node instance with an Operator. An Operator in Kubernetes means that you can declaratively just add a so called “Custom Ressource” and the Operator in the background will take care of “running” the thing. The crucial part is that I needed to do two minor code changes to IoTDB to get it running: * No IP resolution at startup * if the string "hostname" is set as "internal_ip" in iotdb-cluster.properties it will resolve the hostname at startup (FQDN) and set as internal_ip parameter Although the latter is only for comfort and could also be solved differently. Both changes are in the branch https://github.com/apache/iotdb/commits/experimental/0.12.2-cluster-for-k8s. Xiangdong already started a discussion about the first point: https://lists.apache.org/thread.html/r30d1328da57b2ac22792320e37e9cefa2a6127d9d4c64db8b6bbe332%40%3Cdev.iotdb.apache.org%3E You can find all my work so far and a draft Operator (that works!) in my repo https://github.com/JulianFeinauer/iotdb-operator. I would be very grateful for any discussion or remarks to drive this topic further. And please feel free to contact me if you have questions getting the infrastructure up and running! Best Julian
