Release 2024.5.8

Summary

Release 2024.5.8 of Galaxy-Operator contains 2 fixes:

1. Content signing secret is now correctly included in backups and restores.
2. Recently introduced postgresql status check fixed to support managed/external databases.

What's Changed

• fixing signing-secret backup by @aknochow in #117
• fixing signing scripts and configmap to use user-provided names by @aknochow in #118
• postgres: Wait for stateful on managed db by @dsavineau in #120

Full Changelog: 2024.5.1...2024.5.8

Release 2024.5.1

Important

Potentially Breaking change: This release upgrades the database to PostgreSQL 15 and moves to using the sclorg image. Please read the release notes below carefully before upgrading. Please consider backing up by creating a GalaxyBackup prior to upgrading.

Major changes

Upgrading to PostgreSQL 15 and moving to sclorg images by @rooftopcellist in #80. Please see the PR for a full list of changes. Below are the main points.

• Use new v1.34.1 ansible-operator base image and operator_sdk.util 0.5.0 - commit
• The boolean for deleting the old Postgres PVC by default after Postgres upgrade is now fixed - commit
  • postgres_keep_pvc_after_upgrade: false means the old PG13 PVC will be deleted after upgrade by default
• Add checksum for secrets and configmaps to deployments so containers - commit
• Set new postgres configuration secret if managed database. This means you no longer need to delete existing postgres_configuration secrets in the namespace before restoring - commit
• Add initContainer to initial Postgres data volume permissions if needed - commit

This initContainer is not needed for Openshift deployments. It is designed to make permissions changes needed when using the new sclorg postgresql image with k3s deployments that use hostMount style PVC's, as described here. If postgres_data_volume_init is true, an initContainer will run to set the permissions in the postgresql pvc.

This is aimed to easily solve the issue where some users may need to chmod or chown the postgres data volume for user 26, which is the user that is running postgres in the sclorg image.

For example, you can now set the follow on the AWX spec:

spec:
  postgres_data_volume_init: true
  postgres_init_container_commands: |
    chown 26:0 /var/lib/pgsql/data
    chmod 700 /var/lib/pgsql/data

Full Changelog: 2024.4.30...2024.5.1

---

Note about PostgreSQL PVC permissions

Most users will be able to upgrade without issue, but is a chance that some users may hit a permissions issue depending on the permissions of the underlying filesystem used for the PVC's.

If you use k3s with pre-created PVC's or longhorn, you may have an extra manual step to do upon upgrading if you see the following error in the postgres pod's logs upon upgrade.

$ kubectl -n galaxy logs statefulset/<deployment-name>-postgres-15
mkdir: cannot create directory '/var/lib/pgsql/data/userdata': Permission denied

Anywhere you see <deployment-name>, replace it with your Galaxy instance's name (name of the Galaxy custom resource).

Follow these steps to remediate the issue by setting the postgres_data_volume_init parameter true and deleting the new postgres stateful set.

# Patch your Galaxy custom resource
kubectl -n galaxy patch galaxy <deployment-name> --type=merge -p '{"spec": {"postgres_data_volume_init": true}}'

# Delete the new postgres stateful set
kubectl -n galaxy delete statefulset <deployment-name>-postgres-15

This will add the postgres_data_volume_init: true parameter to your Galaxy custom resource, and trigger the operator to re-create the new postgres pod. Your PVC will be unaffected.

Release 2024.4.30

Warning

Upcoming Breaking change: This is the last release that will use PostgreSQL 13 and the dockerhub postgres:13 image. Future releases will use the quay.io/sclorg/postgresql-15-c9s image. Be sure the read the release notes of the next release carefully before upgrading.

What's Changed

• Use docker engine for container build make targets in release GHA by @rooftopcellist in #94
• restore: Move storage_claim fact by @dsavineau in #97
• updating csv by @aknochow in #102
• Add Galaxy logo for operator CSV instead of Pulp logo by @rooftopcellist in #95
• patchesStrategicMerge is deprecated updating to patches by @djdanielsson in #103
• Fix galaxy api root and update csv fields by @aknochow in #104
• adding tasks to remove deprecated routes by @aknochow in #109
• ci: Pin on kubernetes 1.28 by @dsavineau in #115
• fix: make undeploy to respect user-provided namespace by @kurokobo in #112
• Fix issue #110 by @coolhome in #111

New Contributors

• @djdanielsson made their first contribution in #103
• @coolhome made their first contribution in #111

Full Changelog: 2024.4.3...2024.4.30

Release 2024.4.3

Upcoming Breaking change

• This is one of the last release that will use PostgreSQL 13 and the dockerhub postgres:13 image. In a couple releases, will use the quay.io/sclorg/postgresql-15-c9s image. Be sure to read the release notes carefully.

Major Changes:

• There were breaking changes in the galaxy_ng image (via changes in pulpcore). As a result, earlier versions of the Galaxy Operator were not compatible with galaxy-ng after March 22nd, 2024. More context can be found here: ansible/galaxy_ng#2105

What's Changed

• updating README by @aknochow in #68
• updating README and Docs by @aknochow in #69
• fixing logo image path by @aknochow in #70
• adding symlink to images directory for readthedocs by @aknochow in #71
• reverting image path and removing symlink by @aknochow in #72
• setting README image source to full url by @aknochow in #73
• docs: enable search feature by @kurokobo in #76
• fix: add missing nginx snippets for pulp_container by @kurokobo in #75
• feat: add missing snippets for nginx by @kurokobo in #79
• Pin pulp-cli to 0.23.0 for CI temporarily by @rooftopcellist in #82
• Set reasonable default GHA timeout values values by @rooftopcellist in #81
• Makefile: Fix catalog-push with podman engine by @dsavineau in #87
• Remove invalid main image tags from samples by @rooftopcellist in #89
• Remove unnecessary comment by @rooftopcellist in #88
• Variabilize the entrypoint script directory path for all deployments by @rooftopcellist in #90
• Fix entrypoint path for pulpcore scripts by @rooftopcellist in #91
• fix: correct issue with bundle_cacert_secret in api template by @demonpig in #86

New Contributors

• @kurokobo made their first contribution in #76
• @demonpig made their first contribution in #86

Full Changelog: 2024.02.29...2024.04.03

Release 2024.02.29

This is the first release of Galaxy Operator, the official Kubernetes Operator for the Galaxy project.

Breaking change

• In the custom resource, the Kind is now Galaxy instead of Pulp. Refer to the example here.
• If you want to migrate an existing deployment, you can use the migrate_data.yml flow. Docs for this are coming soon to the Galaxy Operator docs. However for now, you can follow the steps from the awx-operator as they will be the same here as well.

Major Changes:

• CustomResourceDefinitions (CRDs) are now Galaxy (galaxies.galaxy.ansible.com), GalaxyBackup (galaxybackups.galaxy.ansible.com), and GalaxyRestore (galaxyrestores.galaxy.ansible.com)
• Galaxy image is now Galaxy-NG (https://github.com/ansible/galaxy_ng)
• Galaxy Web is now Galaxy-UI (https://github.com/ansible/ansible-hub-ui)
• New documentation (https://ansible.readthedocs.io/projects/galaxy-operator)
• Versioning changed to calver format (https://calver.org/)

What's Changed

• Add Galaxy-NG 4.8+ support by @aknochow in #24
• Add community-crypto collection by @rooftopcellist in #27
• Add the community.crypto collection to the correct directory by @rooftopcellist in #28
• Add release automation and multi-arch build support by @rooftopcellist in #32
• Remove pulp-resource-manager config by @dsavineau in #36
• Remove outdated Instant Demo scripts and CI reference by @rooftopcellist in #41
• adding kustomization and galaxy.yaml. Updating bases to resources. … by @aknochow in #44
• Renaming pulp to galaxy. by @aknochow in #46
• Generate a cal-version when releasing if no version is specified by @rooftopcellist in #38
• Renaming pulp to galaxy by @aknochow in #48
• renaming pulp to galaxy inside roles and playbook by @aknochow in #49
• Include galaxy-ng nginx snippets and remove duplicate ones by @rooftopcellist in #51
• Revert nginx conf by @rooftopcellist in #52
• Fix nightly CI runs and reformat GHA workflow by @rooftopcellist in #45
• Validate OLM bundle & remove unneed deploy.sh script by @rooftopcellist in #53
• updating docs by @aknochow in #55
• Install operator-sdk as needed for make targets by @rooftopcellist in #56
• Use operator-sdk binary the make target lays down by @rooftopcellist in #57
• Always ensure /var/lib/pulp/media directory exists via the initContainer by @rooftopcellist in #58
• combine defaults and updating docs by @aknochow in #60
• Fix conditional check for version input on stage workflow by @rooftopcellist in #61
• Break calver generation into a dedicated python script by @rooftopcellist in #62
• Correctly set cal-ver output in stage.yml by @rooftopcellist in #63
• Fix path to calver script for stage.yml by @rooftopcellist in #64
• Add working-directory to path by @rooftopcellist in #65

Full Changelog: 0.15.0...2024.02.29

Release v0.15.0

Prior to this release, this operator lived in the github.com/pulp/pulp-operator repo on the ansible branch. This is the last release that will use the galaxy-minimal and galaxy-web images that were built using the github.com/pulp/pulp-oci-images repo.

Also, please note that this is the last release that will use Pulp, PulpBackup, and PulpRestore CRD names. In the next release, these CRD names will change to be named Galaxy, etc.

Starting with the next release, the galaxy-operator will use the galaxy-ng and galaxy-ui images.