Hi everyone, Eric Helms & I have been working on creating Pulp 3 Kubernetes / container packaging, including a Kubernetes Operator.
This includes each Pulp process (like pulp-content & pulp-worker) running in their own container, and the end goal is for a single Pulp 3 cluster to be scalable (such as for those 2 processes in particular.) Background: About 7 months ago, Eric Helms started working on creating Pulp 3 containers, including a Kubernetes operator. He appropriately named it "carafe": https://github.com/ehelms/carafe But later put much of it in the repo named "pulp-operator" (and continued development there,) and submitted a PR for the 4 pulp containers to be in pulpcore itself. Latest developments: I have been working on updating & finishing this effort. Improvements include: - Compatibility with pulpcore 3.0 rc2 - Persistent Volume storage for MEDIA_ROOT (/var/lib/pulp) Much more work remains, although it is usable enough for a demonstration of Pulp running on Kubernetes in the 1st place (with the pulpcore & pulp-operator PRs.) In the meantime, don't be surprised by the following changes: 1. PRs against pulpcore like this one: https://github.com/pulp/pulpcore/pull/127 2. The pulp-operator repo: https://github.com/pulp/pulp-operator 3. Us putting our CentOS 7 based redis Dockerfile somewhere other than my personal github: https://github.com/mikedep333/carafe/tree/summit-demo Also, note that any DockerHub or Quay.io projects like "carafe" or "mikedep333" are temporary. -Mike
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
