Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Provide Migration Path for Apiserver -> CRDs #2634

Closed
jberkhahn opened this issue May 22, 2019 · 4 comments
Closed

Provide Migration Path for Apiserver -> CRDs #2634

jberkhahn opened this issue May 22, 2019 · 4 comments
Assignees
Milestone

Comments

@jberkhahn
Copy link
Contributor

Description

We need to create a migration guide/scripts which will allow clients to do easily migraton from api-server to CRD approach.

Raw scenario

  • pre-upgrade hook
    • replace the api-server deployment with the api-server that has a read-only mode
    • backup the Service Catalog resources to the persistent volume (consider backuping etcd and second with new format that will be used for restore)
  • upgrade
    • remove the api-server
    • remove the etcd storage
    • adjust secrets, RBAC etc.
    • upgrade controller manager
    • install webhook server
  • post-upgrade
    • scale down the controller manager to 0
    • restore the Service Catalog resources - Spec and Status (status is important because we do not want to trigger provisioning for already process items)
    • scale up controller manager

AC

  • upgrade with migration only if previous SC version has api-server, and explicitely flag with migration is set to true
  • migration from the Aggregated API Server to CRD approach is doable and well documented
@jberkhahn jberkhahn added this to the 0.3.0 milestone May 22, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 20, 2019
@mszostok mszostok removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2019
@mszostok
Copy link
Contributor

/assign

@mszostok
Copy link
Contributor

the story was mainly resolved by #2710

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

No branches or pull requests

4 participants