Upcoming changes to Galaxy and EDA operator releases

Project Discussions
, , , , ,
1

As part of our broader modernization and refactoring effort for AWX and its operator, we have stopped making tagged releases on GitHub. This approach will also be applied to the following operators:

  • eda-server-operator
  • galaxy-operator

For more details on why we have chosen this shift in release strategy, please refer to the AWX community post:

:link: Upcoming changes to AWX operator installation methods

Current Publishing Strategy

We now push operator images to quay.io publicly using commit SHA tags rather than traditional versioned tags.

To install the latest version of the eda-server-operator, users should:

  1. Clone the main branch
  2. Use make deploy or kustomize to run the operator

Installing from a Specific Commit

If you want to install a specific version of an operator, you can still do so by referencing the exact commit:

EDA Server Operator

  1. Clone the eda-server-operator repository
  2. Checkout the desired commit
  3. Deploy using make deploy
  4. Create an EDA custom resource

Note: It may be helpful to pin to container images built on the same day. You can do this by specifying the image, image_version, image_web, and image_web_version parameters on the CR for the following container images:

Galaxy Operator

  1. Clone the galaxy-operator repository
  2. Checkout the desired commit
  3. Deploy using make deploy
  4. Create a Galaxy custom resource

Note: It may be helpful to pin to container images built on the same day. You can do this by specifying the image, image_version, image_web, and image_web_version parameters on the CR for the following container images:

Thanks,
The Ansible Team