Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for component-backup-k8up v3.0.0 #121

Open
britdm opened this issue Sep 23, 2022 · 2 comments
Open

Support for component-backup-k8up v3.0.0 #121

britdm opened this issue Sep 23, 2022 · 2 comments

Comments

@britdm
Copy link

britdm commented Sep 23, 2022

In v3.0.0 for component-backup-k8up the default CRDs for backups switches from backup.appuio.ch to k8up.io, and changes the apiVersion from backup.appuio.ch/v1alpha1 to k8up.io/v1.

Proposing a change to the apiVersion in schedule.yaml to support deployments that are using v3.0.0.

@tobybellwood
Copy link
Member

We've looked at this, and when we bring the k8up into build-deploy tool, we'll look at supporting both the v1 and v2 versions.

@tobybellwood
Copy link
Member

expanding a bit further on this:

Lagoon will likely support both k8up versions simultaneously to allow users to gradually transition if they prefer. This would likely mean that any new deployments automatically update the crds used to v2. In order for all namespaces to be v2 compliant, a script would have to be written to recreate all the k8up CRDs in a namespace for v2.

Upgrading in-place could be possible, but it would likely be safer to install v2 in a separate namespace alongside v1. If we develop additional guidance on this, it will be included as part of the install notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants