kubevirt PR #1550

[Alexander Gallego]

Hi David, 

I saw the first iteration of migration was merged. 

https://github.com/kubevirt/kubevirt/pull/1550

This is really exciting step forward and wanted to start a brainstorm discussion on how to allow hooks into the migration. --> user hooks.

Before a migration happen, on our cluster we have to do a dance to move secrets around and hook into our KMI (key management infra). 

Extending the VM lifecycle hooks would be a natural point, but wanted to ask if you are considering exposing this to clients and how. 

.alex

[dvo...@redhat.com]

The migration flow looks roughly like this.

1. cluster level - Create target pod

2. target node - prepare target pod (setting up network and creating ephemeral disks for things like cloud-init)

3. source node - perform migration

4. source node - hand off VMI object to target node

5. cluster level - source pod tears down

It's possible to add lifecycle hooks for items 2, 3 and 4.  Which hooks would you need to satisfy your use case?

 

.alex