Kubernetes Cluster Control Deployment nodes fail to join

Hi,

I'm currently experimenting with the kubernetes setup and so far I manged to get the deployment runniung but it always fails to join the nodes to the cluster. The first seems to be running fine, at least I can see a green checkmark in cluster control. I followed this guide: https://severalnines.com/database-blog/running-galera-cluster-clustercontrol-kubernetes. I had to create a new container image based on CentOS7 since the one provided by S9 is based on CentOS6 which is now EOL but this was not a big deal. I get as far as running cluster control and then the bootstrap process is starting and the first node (pod) works fine but the other two nodes are failing to join the cluster. Looking at the Job Log in Cluster Control I can see a couple of errors, but I'm not sure whether these are the actual problem.The create Galera Cluster job finishes successfully, but there are a couple of errors during execution:

• [16:04:10]:
  10.42.0.3: Output iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
  Perhaps iptables or your kernel needs to be upgraded.
  .
• [16:04:10]:
  10.42.0.3: Command was /sbin/iptables -F.
• [16:04:10]:
  10.42.0.3: Execution failed with return code 3.

• [16:04:10]:
  10.42.0.3: Output iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root)
  Perhaps iptables or your kernel needs to be upgraded.
  .
• [16:04:10]:
  10.42.0.3: Command was /sbin/iptables -F.
• [16:04:10]:
  10.42.0.3: Execution failed with return code 3.

• 15:55:17]:
  10.36.0.2: Output Failed to get D-Bus connection: Operation not permitted
  .
• [15:55:17]:
  10.36.0.2: Command was systemctl --no-pager --full status mariadb 2>&1.
• [15:55:17]:
  10.36.0.2: Execution failed with return code 1.
• [15:55:17]:
  10.36.0.2: Started MySQL daemon.
• [15:55:12]:
  10.36.0.2: nohup: ignoring input and appending output to 'nohup.out' (exit code: 1)
• [15:55:12]:
  10.36.0.2: Output Failed to get D-Bus connection: Operation not permitted
  .
• [15:55:12]:
  10.36.0.2: Command was systemctl --no-ask-password daemon-reload.
• [15:55:12]:
  10.36.0.2: Execution failed with return code 1.
• [15:55:09]:
  10.36.0.2: Output Failed to get D-Bus connection: Operation not permitted
  .
• [15:55:09]:
  10.36.0.2: Command was systemctl --no-ask-password daemon-reload.
• [15:55:09]:
  10.36.0.2: Execution failed with return code 1.

So it seems it is failing to start mysql, but on the first node mysql is running fine after the deployment. Maybe the errors are related due to the fact that it is running in a container and there is no systemd?

Would be really cool to have a working cluster. Has anyone succeeded in deploying this?

Best Regards,

Oliver