Story #8513: pulp-operator should be able to restore a pulp deployment - Pulp

Actions

Story #8513

closed

Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

Category:

Operator - Moved to Github Issues

Sprint/Milestone:

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

Introduce a PulpRestore CRD that the operator can watch.

Processing of a Pulp Restore custom resource will:

Create necessary secrets like database, admin password, object storage (if applicable)
Create a Pulp CR
Restore the database content using the PGDump stored file
If using file storage, it will mount a management pod to the RWM file claim and copy the data into place

Actions

Actions

Enable restore of deployment associated with Pulp custom resource backup

Update backup CRD to contain deployment name and secret names
Update CSV with entries for backup fields and fix field label consistency
Create restore CRD
Update CSV with entries for restore CRD
Update up.sh and down.sh to create restore CRD
Update watches file with the new restore role
Updates to backup role to add status values and convert stored secrets and CR for restore

Actions