Using the custom init image

Starting from v0.18.1, the ArtemisCloud Operator enables you to specify a custom Init Container image. Specifying a custom Init Container image allows you to provide your own broker configuration within the Operator framework.

What is a custom Init Container image?

The ArtemisCloud Operator uses a Custom Resource Definition (CRD) to define the broker configuration. In Kubernetes, a CRD is a schema of configuration items or parameters. By creating a corresponding Custom Resource (CR) instance, you can specify values for configuration items in the CRD. For example, you can define address settings in this sample CR file.

For configuration that isn’t exposed in the CRD, you can specify a custom Init Container image to manipulate or add to the configuration that has been created by the Operator. When the CR is deployed and the broker instance is created, the Operator will then run a user-provided post-configuration script.

How it works

Internally, the ArtemisCloud Operator uses a specialized container called an Init Container to configure each broker instance. If no custom image for the Init Container has been specified, the Operator uses a built-in Init Container image, which is responsible for the configuration. The broker configuration generated by the Init Container is passed to the broker container image to use when launching the broker.

If a custom Init Container image is provided and specified in the Custom Resource (CR), then this is used to create the configuration. Since the custom image is built on top of the ArtemisCloud built-in Init Container image, the custom image first generates the broker configuration that is defined in the CR. Then, the Operator executes the post-configuration ( script provided by the custom Init Container.

For ease of use, the environment variable CONFIG_INSTANCE_DIR is set. This environment variable points to the broker instance directory, which has the following structure:


When the script is invoked, the directory specified in CONFIG_INSTANCE_DIR already contains all of the configuration files generated by the built-in image (via the configuration specified in the CR) and is available for the script to do extra configuration.

For example, a custom Init Container might be used to modify the logging settings and add or override some specific configurations in ${CONFIG_INSTANCE_DIR}/etc. In addition, the custom Init Container might put extra runtime dependencies (.jar files) in the ${CONFIG_INSTANCE_DIR}/lib directory so that the broker can use them.

After the script is executed, the broker instance is launched with the updated configuration.

Specifying a custom Init Container image

  1. First, you need to implement your custom Init Container image.

    The custom image should follow these predefined rules:

    • The custom image must include a script in the /amq/scripts directory. The absolute path will be /amq/scripts/

    The script is where you modify the configuration of the broker or add any third party dependencies.

    If you need additional resources (.xml files, .jar files, etc.) for your custom configuration, you need to add them to your image and make sure that they are accessible to your post-config scripts.

  2. Next, you need to build your custom Init Container image and put it in a container repository (for example you can create a repository on Red Hat Quay).

  3. When you have added the image to a repository, you need to configure the Operator to use the custom Init Container image. To do this, edit the CR file. For the image property, specify the custom image. For example:

    kind: ActiveMQArtemis
        name: ex-aao
                size: 1
                initImage: <your_custom_init_image_url>
  4. Finally, deploy the CR file in the usual manner. For more information, see Getting Started with the ArtemisCloud Operator.

Further information

  • A fully working example is available here.

  • For issues or suggestions please open an issue at ArtemisCloud.