Changing Fleio Docker images used in kubernetes

Warning

Fleio in kubernetes is still in beta, and is not intended for production use.

Creating custom docker images for Fleio

For a general overview of the Fleio kubernetes deployment, see Fleio in kubernetes first.

Fleio can be customized by creating custom docker images with your change.

To create custom Fleio docker images, please see Adding or changing files in Fleio Docker images.

Once you have built your custom docker images, you need to upload them to a docker registry accessible from your kubernetes cluster, then follow the instruction in the next section to use your custom images.

Using custom docker images for Fleio

Using deployment overrides

A Fleio deployment can be configured to use custom images. Assuming you built a custom utils image and uploaded it to a custom registry named registry.example.com under the name fleio_custom_utils you will need to add the following to your Fleio deployment either by editing the .yaml file and (re)applying it, or by using kubectl edit fleiodeployment command:

  advanced:
    deploymentsOverrides:
      utils:
        imagePath: "registry.example.com/fleio_custom_utils"
        imagePullSecret: 'docker-credentials-secret'

Using a custom registry

Another way to use custom images in Fleio is to pull all unchanged images from hub.fleio.com and upload them to a custom registry along with your updated images. You will need to use our naming convention for images (e.g., utils image for Fleio 2024.04.1 release should be named fleio_utils-2025-04:1).

Once you have this custom registry prepared, you will need to add the following to your Fleio deployment either by editing the .yaml file and (re)applying it, or by using kubectl edit fleiodeployment command (replace registry.example.com with your custom registry URL):

  advanced:
    customDockerRegistry: registry.example.com