Sample Configs¶
To help with the first steps of Pulp installation and CR definition, there are a set of samples in pulp-operator repository.
MINIMAL CONFIGURATION¶
The minimal.yaml file, provides a sample CR with
the minimal configurations needed (the database and pulpcore storage definitions) for the operator to run. It will deploy Pulp with a single replica of pulpcore pods and a random password for the admin user.
Note
The minimal.yaml sample will not deploy a reverse proxy or expose pulpcore pods.
SIMPLE¶
The simple.yaml file, provides a sample CR
that will deploy Pulp with:
- a single replica of pulpcore pods
- a definition of the StorageClass to store Pulp artifacts
- a database pod
- a cache pod
- a k8s Service type nodeport
- a pre-defined password for the admin user
- some Pulp app configs (settings.py definitions)
S3¶
The simple.s3.ci.yaml file, provides a sample CR
that will deploy Pulp with:
- a single replica of pulpcore pods
- an object storage (S3) to store Pulp artifacts
- a database pod
- a k8s Service type nodeport
- a pre-defined password for the admin user
- some Pulp app configs (settings.py definitions)
EXTERNAL DATABASE¶
The simple-external-db.yaml file, provides a sample CR
that will deploy Pulp with:
- a single replica of pulpcore pods
- a definition of the StorageClass to store Pulp artifacts
- a definition of a k8s Secret with the credentials to access a postgres database (not deployed/managed by pulp-operator)
- a k8s Service type nodeport
- a pre-defined password for the admin user
- some Pulp app configs (settings.py definitions)
INGRESS¶
The simple.ingress.yaml file, provides a sample CR
that will deploy Pulp with:
- a single replica of pulpcore pods
- a definition of the StorageClass to store Pulp artifacts
- a database pod
- some Pulp app configs (settings.py definitions)
- a k8s ingress