Running Pulp in k8s without operator using cloud services (S3/Redis/Postgres).
Pulp is deployed in k8s using helm charts without an operator.
Pulp plugins installed and their versions:
Operating system - distribution and version:
Other relevant data:
Hey folks, I was interested in the Pulp project and I want to spin it up in the Kubernetes environment.
As I could see there is a k8s operator: https://github.com/pulp/pulp-operator
but I am curious about deploying pulp without the operator since I can use some external cloud services like Postgres, Redis, S3 storage, and so on for application state.
I wonder if you could suggest if it is reasonable to spin up the pulp application using the external “state services” and using helm charts for pulp application.
In other words - does the pulp (or it’s core modules/plugins especially like Deb/RPM), store state anywhere (instead of redis/posgres)? Can I avoid using the operator or there are any pitfalls?
I’d really appreciate any advice.