Red Hat Marketplace Requirements
A walk through of the changes required to enable your operator to work in an offline environment. This is also a technical requirement for Red Hat Marketplace.
Last updated
Was this helpful?
A walk through of the changes required to enable your operator to work in an offline environment. This is also a technical requirement for Red Hat Marketplace.
Last updated
Was this helpful?
You can find an .
Make sure your Helm chart only references the values file for images. Each image should be a single value (it can't be split into repository and tag, for example).
A great way to find all the parts of your helm chart that will need to be updated is to recursively search your project's template folder for "image:"
Here we see that the image is split into two values - repository and tag. This won't work because we need to have a single variable to override. Replace this line with a new, single variable:
Don't forget to add this new value to your Values.yaml file!
In the watches.yaml file, add a field for overrideValues. It should contain each variable from the values.yaml file that corresponds to an image, and should be set to the environment variable you want to use.
NOTE: the variable name MUST follow the pattern RELATED_IMAGE_. There is code looking for that string in your operator.
Make sure your role is using environment variables for images instead of hard-coded or regular variables. If it's not, update it:
Above you can see a reference to a image that's defined in the role's defaults/main.yaml file with an option to override it in values/main.yaml. Instead, use Ansible's lookup module to reference an environment variable and remove the variable from defaults/main.yaml to avoid confusion:
NOTE: Your environment variables need to follow the RELATED_IMAGE_ format, as there is code looking for this pattern.
Make sure your code is using environment variables for any images your operator uses (any image except the operator itself).
In the CSV and operator.yaml files, declare the variable and set to a default value.
If you're in the habit of using the "latest" tag for your images, make sure you specify it. Because of how the automation is written that picks up these images, we need a tag to be present.
Make sure you aren't overwriting the image in your CR (and by extension in the alm-examples field of the CSV). The best way to handle this is removing the field from the CR/alm-examples.
Using operator-sdk version 0.14.0 or later, build the updated operator image, and skip down to the
You can find an .
Build your updated operator image, and skip down to the
You can find an .
Build your updated operator image, and skip down to the
If you want to use the entitled registry for Red Hat Marketplace, your images must be hosted in .
You will need to scan your operator with the docker images using , replacing all your image references to use this docker registry.
From there, apply an ImageContentSourcePolicy to point to . This will allow the marketplace operator to use the entitled registry and properly replace the image strings.