Katello/Pulp-Community Integration meeting minutes

2026-10-06 1000-1030 GMT-5

Attendees: ggainey, quba42, mbucher, sjha

Regrets:

Agenda:

  • Previous AIs:
  • Does this affect Katello? (Need to run pulpcore-manager container-repair-pull-through-distributions “before upgrading pulpcore”) Changelog - Pulp Project
    • get full low-level details from Gerrod if you want
    • katello is updating foreman-ctl to handle this upgrade scenario along with the container-repo-type-merge upgrade
  • pulp-replication, smart-proxies, and pulp_deb - discuss
    • pulp-replication does not support pulp_deb yet - should we panic?
    • this is currently an idea, not yet a Plan
    • do we even have a Jira for this somewhere?
  • [ATIX] We heard on the wind, that there are plans to add SBOM data to packages / or repositories to fulfill the Cyber Resilience act for June 2027. Do you know more?
    • required for “Champion” status
    • we’d like to do that “eventually”, but currently only required to do “Light” stewardship for regulatory obligations (and have completed the “Light” stewardship requirements)

Action Items:

1 Like

2026-11-03 1000-1030 GMT-5

Attendees: mbucher, bsuttner, ggainey, pbrochado, iballou

Regrets:

Agenda:

  • Previous AIs:
  • PulpCon 2026 Schedule published!!!
  • Pulp supported branch policy discussions
    • idea of pulp deciding beforehand what will be a supported branche
    • example: always the release before the 15 Y-release cycle (plugin breaking change)
  • Katello wanting to explore the container area
  • Performance issues around incremental-updates of CCVs
    • Pulp is doing a lot of investigation/fixes around large-scale performance right now - stay tuned!
    • discussion ensues

Action Items:

1 Like