Open Source tooling, such as for managing the state of Pulp and integrating it with other projects, that is either maintained by the commnunity or other projects, or that is developed by the Pulp Project but not yet in production.
Foreman / Katello
Foreman is a complete lifecycle management tool for physical and virtual servers. Katello brings the full power of content management alongside the provisioning and configuration capabilities of Foreman.
Foreman and Katello use Pulp for managing repositories of software packages. It provides a graphical WebUI for Pulp and integrates it with its workflows, but does not expose every underlying feature and content type of Pulp.
Foreman and Katello are currently in the incremental process of migrating from Pulp 2 to Pulp 3.
Ansible Modules for Pulp aka Squeezer
This project provides Ansible modules (currently only for pulp-file) to control a Pulp 3 server in a descriptive way. This is neither to be confused with the Pulp 3 Ansible Installer pulp_installer (a collection of Ansible roles to install Pulp), nor pulp_ansible (a Pulp content plugin to manage Ansible content in Pulp.)
This Ansible role interacts with a Pulp 3 server. It helps to create and manage rpm repositories.
pulp-operator: Kubernetes Operator for Pulp 3
A Kubernetes Operator for Pulp 3, under active development (not production ready yet) by the Pulp team. The goal is to provide a scalable and robust cluster for Pulp 3. Pre-built images are hosted on quay.io.
Note that it utilizes a single container image from the pulpcore repo, to run 4 different types of service containers (like pulpcore-api & pulpcore-content.) currently manually built and hosted on quay.io.
It is currently working towards Phase 1 of the Kubernetes Operator Capability Model before being published on OperatorHub, including compatibility with more clusters.
See latest slide deck for more info.
A script to install Pulp 3 on Linux systems with as many plugins as possible and an uninstaller.
Works by installing K3s (lightweight kubernetes), and then deploying pulp-operator on top of it.
Is not considered production ready because pulp-operator is not yet, it hides every config option, and upgrades are not considered. Only suitable as a quick way to evaluate Pulp for the time being.