galaxy-operator

Galaxy-Operator

GPL-2.0 License

Stars
5
Committers
27

Bot releases are visible (Hide)

galaxy-operator - Release 2024.5.8 Latest Release

Published by github-actions[bot] 6 months ago

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

Full Changelog: https://github.com/ansible/galaxy-operator/compare/2024.5.1...2024.5.8

galaxy-operator - Release 2024.5.1

Published by github-actions[bot] 6 months ago

[!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 https://github.com/ansible/galaxy-operator/pull/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: https://github.com/ansible/galaxy-operator/compare/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.

galaxy-operator - Release 2024.4.30

Published by github-actions[bot] 6 months ago

[!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

New Contributors

Full Changelog: https://github.com/ansible/galaxy-operator/compare/2024.4.3...2024.4.30

galaxy-operator - Release 2024.4.3

Published by github-actions[bot] 7 months ago

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.

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: https://github.com/ansible/galaxy_ng/pull/2105

What's Changed

New Contributors

Full Changelog: https://github.com/ansible/galaxy-operator/compare/2024.02.29...2024.04.03

galaxy-operator - Release 2024.04.03

Published by github-actions[bot] 7 months ago

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.

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: https://github.com/ansible/galaxy_ng/pull/2105

What's Changed

New Contributors

Full Changelog: https://github.com/ansible/galaxy-operator/compare/2024.02.29...2024.04.03

galaxy-operator - Release 2024.02.29

Published by github-actions[bot] 8 months ago

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:

What's Changed

Full Changelog: https://github.com/ansible/galaxy-operator/compare/0.15.0...2024.02.29

galaxy-operator - Release v0.15.0

Published by rooftopcellist 8 months ago

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 1.0.0 release to come, 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.

Related Projects