5.22.3. Restoring 3scale API Management by using OADP

Procedure

1. Delete the 3scale operator custom resource definitions (CRDs) along with the threescale namespace by running the following command:

   $ oc delete project threescale

   "threescale" project deleted successfully

2. Create a YAML file with the following configuration to restore the 3scale operator:

   apiVersion: velero.io/v1
   kind: Restore
   metadata:
     name: operator-installation-restore
     namespace: openshift-adp
   spec:
     backupName: operator-install-backup
     excludedResources:
     - nodes
     - events
     - events.events.k8s.io
     - backups.velero.io
     - restores.velero.io
     - resticrepositories.velero.io
     - csinodes.storage.k8s.io
     - volumeattachments.storage.k8s.io
     - backuprepositories.velero.io
     itemOperationTimeout: 4h0m0s

   where:

   operator-install-backup

   Specifies the name of the backup to restore the 3scale operator.

3. Restore the 3scale operator by running the following command:

   $ oc create -f restore.yaml

   restore.velerio.io/operator-installation-restore created

4. Manually create the s3-credentials Secret object by running the following command:

   $ oc apply -f - <<EOF
   ---
   apiVersion: v1
   kind: Secret
   metadata:
         name: s3-credentials
         namespace: threescale
   stringData:
     AWS_ACCESS_KEY_ID: <ID_123456>
     AWS_SECRET_ACCESS_KEY: <ID_98765544>
     AWS_BUCKET: <mybucket.example.com>
     AWS_REGION: <us-east-1>
   type: Opaque
   EOF

   where:

   <AWS_ACCESS_KEY_ID>

   Specifies your AWS credentials ID.

   <AWS_SECRET_ACCESS_KEY>

   Specifies your AWS credentials KEY.

   <mybucket.example.com>

   Specifies your target bucket name.

   <us-east-1>

   Specifies the AWS region of your bucket.

5. Scale down the 3scale operator by running the following command:

   $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=0 -n threescale

   deployment.apps/threescale-operator-controller-manager-v2 scaled

6. Create a YAML file with the following configuration to restore the Secret:

   apiVersion: velero.io/v1
   kind: Restore
   metadata:
     name: operator-resources-secrets
     namespace: openshift-adp
   spec:
     backupName: operator-resources-secrets
     excludedResources:
     - nodes
     - events
     - events.events.k8s.io
     - backups.velero.io
     - restores.velero.io
     - resticrepositories.velero.io
     - csinodes.storage.k8s.io
     - volumeattachments.storage.k8s.io
     - backuprepositories.velero.io
     itemOperationTimeout: 4h0m0s

   where:

   operator-resources-secrets

   Specifies the name of the backup to restore the Secret.

7. Restore the Secret by running the following command:

   $ oc create -f restore-secrets.yaml

   restore.velerio.io/operator-resources-secrets created

8. Create a YAML file with the following configuration to restore APIManager:

   Example restore-apimanager.yaml file

   apiVersion: velero.io/v1
   kind: Restore
   metadata:
     name: operator-resources-apim
     namespace: openshift-adp
   spec:
     backupName: operator-resources-apim
     excludedResources:
     - nodes
     - events
     - events.events.k8s.io
     - backups.velero.io
     - restores.velero.io
     - resticrepositories.velero.io
     - csinodes.storage.k8s.io
     - volumeattachments.storage.k8s.io
     - backuprepositories.velero.io
     itemOperationTimeout: 4h0m0s

   where:

   operator-resources-apim

   Specifies the name of the backup to restore the APIManager.

   excludedResources

   Specifies the resources that you do not want to restore.

9. Restore the APIManager by running the following command:

   $ oc create -f restore-apimanager.yaml

   restore.velerio.io/operator-resources-apim created

10. Scale up the 3scale operator by running the following command:

    $ oc scale deployment threescale-operator-controller-manager-v2 --replicas=1 -n threescale

    deployment.apps/threescale-operator-controller-manager-v2 scaled