Best practices for setup tool in a cluster (Kubernetes)

Submitted by enrico.curiotto on Tue, 05/18/2021 - 16:41
1
0
-1

Hello,

let's suppose we have a kubernetes cluster with 3 bonita nodes, and the database on a separate machine.

What are the best practices for the setup tool?

As a reminder the setup tool is a java jdbc tool that

  1. allows to configure the engine through some configuration files
  2. is used to update/install Bonita licences
  3. Some files of the setup folder are used by the engine at startup for some tomcat configuration (tomcat_templates folder)

Is it ok to install only the setup tool on a 4th node, and to remove it from the 3 pods?

Or it's better to leave it on all the pods ? Are the setup/tomcat_templates used in a kubernetes cluster?

Thanks

1 answer

Submitted by Truc on Mon, 06/07/2021 - 10:57
1
+1
-1
This one is the BEST answer!

Hello,

I think both options can be considered, depending on your requirements and use cases.

The setup tool can remain with the Bonita pods, and it can be executed before the Tomcat startup for instance, each time a Bonita pod is launched. This option does not require a new Docker image, as the setup tool could be invoked within "custom-init.d" scripts (these are entry points that are provided by the Bonita Docker image). Then the configuration actions and Bonita restarts would be handle within the same operation, which is to restart the Bonita pods.

On the other hand, the setup tool could also be deployed on a separate pod. This would require to create a new Docker image which embeds the setup tool only I guess. Then to apply the changes, you would have to restart the Bonita pods.

Hope this helps.

Notifications