cluster-api-provider-microvm icon indicating copy to clipboard operation
cluster-api-provider-microvm copied to clipboard

Upgrading from CAPMVM 0.4.0 to 0.7.0 requires updates to the cluster objects

Open LutzLange opened this issue 2 years ago • 2 comments

What happened: I did update to flintlock v0.2.0 and capmvm v0.7.0 from capmvm v0.4.0

The schema did change in a few places and updates to my existing cluster templates and cluster objects in git were required.

From the single sshPublicKey to sshPublicKeys. I used these commands :

  1. Remove lutz@dellbook on separate lines $ sed -i 's/^ *lutz@dellbook//' clusters/management/clusters/*.yaml
  2. Match & replace sshPublicKey with sshPublicKeys $ sed -i -e 's/^ sshPublicKey: \(.*\)/ sshPublicKeys:\n - user: root\n authorizedKeys:\n - \1/' clusters/management/clusters/*.yaml
  3. Remove mountpoint entries for the rootVolumes $ sed -i '/^ *mountPoint:/d' ~/git/demo3-repo/clusters/management/clusters/*.yaml Updating CAPI templates :
  4. sshPublicKeys $ sed -i -e 's/^ sshPublicKey: \(.*\)/ sshPublicKeys:\n - user: root\n authorizedKeys:\n - \1/' capmvm-*.yaml
  5. Provider-id $ sed -i 's#provider-id:.*#provider-id: "microvm://{{ ds.meta_data.vm_host }}/{{ ds.meta_data.instance_id }}"#' capmvm-*.yaml
  6. Mountpoint issue $ sed -i '/^ *mountPoint:/d'

It might be helpful for others that face the same situation.

LutzLange avatar Aug 19 '22 10:08 LutzLange

This is not a bug, but I can't remove that label.

LutzLange avatar Aug 19 '22 10:08 LutzLange

🙌 thanks lutz, i'll update the labels

Callisto13 avatar Aug 19 '22 13:08 Callisto13