Next Pulp upgrade - Katello 5.1

Development Releases
,
1

Hello community,

I am writing this post in the hopes of starting a tradition of announcing earlier when the next Pulp Y (or X for Pulp 4) upgrade is going to happen.

At the moment, Pulp is planned to be upgraded in Katello for Katello 5.1. Development of Katello 5.1 will start after 5.0 branches on August 11 (8/11). At that point, we will begin conversations with the Pulp team about what version they’d like us to pick up, since it will become one of their long term support releases.

For some news on the Pulp upgrade, we found out that “container push” repositories in Pulp are going to be merging with normal container repositories. While this should make Katello’s management of container repositories much easier, we will need to fix and possibly redo the current “container push” design. We have time to plan it out since Pulp Container is first going to introduce a migration and will continue supporting container push repositories for some time.

Please use this space to discuss other Pulp upgrade concerns and requirements.

Thanks!

5 Likes
Release Team Meeting 2026-09-09
Release Team Meeting 2026-08-26
Release Team Meeting 2026-09-02
Release Team Meeting 2026-08-19
2

Since Katello 5.1 development has begun, we are planning on upgrading Pulpcore to at least version 3.117, or whatever is latest. The upgrade should begin in around a month or earlier.

Pulp Container is moving away from push repositories, which is great because we had to complicate our repository management to accommodate container push repositories in Pulp. See the Pulp Container 2.29 changelog.

This means that, at the same time as our upgrade, we will likely need to use the new migrate endpoint for Pulp Container to get away from push repositories. We’ll need to see what this means for changes to our container registry code.

2 Likes
3

I would like to release a pulp_deb 3.11.0 for inclusion in the new pulpcore version repo. The pulp_deb main branch has unreleased DB migrations I would like to see included.

I am hoping to perform this release by the end of next week (2026-08-21). This gives us some time for a few more reviews and merges before then.

3 Likes
4

Sounds good @quba42 , we’ll make sure that the new release of pulp_deb is included.

5

I ran my self imposed deadline, and now I am trying to review and merge Allow users to specify distribution and component when modifying content by daviddavis · Pull Request #1492 · pulp/pulp_deb · GitHub before the next release.

Please prod me if I am running out of time!

1 Like
6

Bumping a plugin y-version is easier than bumping a Pulpcore y-version, so to be safe let’s say to have it ready 1 month before branching, which puts us at October 10th.

7

pulp_deb 3.11.0 is available on pypi: pulp-deb · PyPI

:blush:

2 Likes
8

We will be starting the upgrade process this week and try to wrap it up in a month. Finalizing the versions we are targeting here:

pulpcore: 3.117.1
pulp-rpm: 3.39.0
pulp-container: 2.29.0
pulp-ansible: 0.30.0
pulp-python: 3.36.2
pulp-deb: 3.11.0
pulp-ostree: 2.6.1

Let me know if these look right.

4 Likes
9

I released pulp-deb 3.11.1 to fix a silly bug I introduced during review of a new feature in 3.11.0.
:innocent:

1 Like
10

Thanks for the update. These are the new versions tagged in our dev image with that version. It currently lives here Quay as we perform all the upgrade dev tasks.

pulpcore: 3.117.1
pulp-rpm: 3.39.0
pulp-container: 2.29.0
pulp-ansible: 0.30.0
pulp-python: 3.36.2
pulp-deb: 3.11.1
pulp-ostree: 2.6.1
1 Like
11

Looks like we need to also update pulp-smart-proxy, since the version that we use now makes new version of pulp unsupported.

12

I’ve fixed up pulp_smart_proxy CI (see Update CI files for branch develop by theforeman-bot · Pull Request #71 · theforeman/pulp_smart_proxy · GitHub) so you should be good to go to bump the bounds

1 Like