[kots]: allow for backup of resources in KOTS

[mrsimonemms]

Description

Allows for triggering snapshots of your application in KOTS.

IMPORTANT this only backs up the KOTS application status. It does NOT backup data in your Gitpod database, registry or object storage. For production instances, we always recommend using external cloud resources - consult with your provider for advice on backing up those resources.

See docs ticket

Related Issue(s)

Fixes #9926

How to test

• Install via KOTS
• Create your Velero instance (see below or I can help with this)
• Create a backup
• Delete Gitpod/KOTS from your cluster
• Restore it to your cluster

Creating your Velero instance

Velero maintains AWS, GCP and Azure as first-class citizens

1. Following the GCP setup instructions
2. The velero install command in the docs needs to have --use-restic appended to it, ie

velero install \                                           
    --provider gcp \
    --plugins velero/velero-plugin-for-gcp:v1.5.0 \
    --bucket $BUCKET \
    --secret-file ./credentials-velero \
    --use-restic \
    --wait

Create a backup

Either:

• In the KOTS Dashboard, click "full snapshot"
• In the CLI, run kubectl kots backup -n gitpod

Restoring a Backup

1. Ensure you have no gitpod or velero namespace on your cluster (this simulates a fresh cluster)
2. Install Velero using the velero install command above
3. Run kubectl kots backup ls and select the backup ID you want
4. Run kubectl kots restore --from-backup <backup-id>
5. Run kubectl kots admin-console -n gitpod
6. In your KOTS Dashboard, hit "redeploy"

After a few minutes, you should have everything restored.

Release Notes

[kots]: allow for backup of resources in KOTS

Documentation

Werft options:

• /werft with-preview

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sub></sup>

[corneliusludmann]

Looks good. Small change, big impact. 🚀