[Feature] Upgrade guidelines for production deployment

[Sharathmk99]

[Feature] Upgrade guidelines for production deployment

[frisso]

This feature is becoming very very important; thanks for opening a feature request..
We should decide when to add this to the roadmap, likely after release 0.9 (whose features have already been decided).
If anybody wants to contribute to this feature, which definitely requires a non negligible amount of work, please add your rocket here :-)

[Sharathmk99]

I would be happy to be part of this effort. It’s very important feature for us. Thanks

[Sharathmk99]

Today tried to upgrade limo version from 0.8.1 to 0.8.3, all core services were fine. But how can I force the virtual-kubelet pod in all remote cluster namespace to use latest version 0.8.3 now?
If I delete the deployment will limo-controller automatically recreates the deployment? Or the only way is to unpeer and peer again?

[ryan-beisner]

Adding rockets :-) 🚀 🚀 🚀 Definitely something needed for prod.

[cheina97]

Today tried to upgrade limo version from 0.8.1 to 0.8.3, all core services were fine. But how can I force the virtual-kubelet pod in all remote cluster namespace to use latest version 0.8.3 now? If I delete the deployment will limo-controller automatically recreates the deployment? Or the only way is to unpeer and peer again?

Hi @Sharathmk99, this is one of the collateral features that will be introduced with VirtualNode CRD. For the moment we suggest to unpeer and peer again.

[frisso]

@Sharathmk99 I know that the previous answer is not a good news for you. On the good side, we're taking this into high consideration for the post-0.9 release.

[Sharathmk99]

Thank you @frisso & @cheina97 for the update and considering this feature for post 0.9 release. I’m looking forward for Virtual Kubelet CRD for better upgrade process.