Helm 2to3迁移,成功迁移后是否要运行Helm Delete? [英] Helm 2to3 migration, do I run helm delete after successful migration?

查看:55
本文介绍了Helm 2to3迁移,成功迁移后是否要运行Helm Delete?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已使用基于以下博客的 helm 2to3 插件成功地从头盔版本2迁移到了头盔3: https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/

I have successfully migrated from helm version 2 to 3 using the helm 2to3 plugin based from the blog here: https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/

运行 helm list helm3 list 时,我都看到了两个发行版/应用程序.我是否需要运行 helm delete< release_name> 来验证该应用程序是否在版本3下运行?

I see both releases/apps when running helm list and helm3 list. Do I need to run the helm delete <release_name> to verify that the app is running under version 3?

更新时间:7/29

我使用 helm delete< release_name> 进行了删除,并且helm2版本/应用被删除了.在helm2中,我列出了应用程序,状态为已删除".但是在helm3中说已部署".它还删除了吊舱.我认为它只会删除helm2下的发行版,而不会影响到pod.在这种情况下,helm3状态是错误的.

I deleted using helm delete <release_name> and the helm2 release/app got deleted. In helm2, I list the apps, the status says "deleted" but in helm3 it says "deployed". It also the deleted the pods. I thought it will only delete the release under helm2 and should not affect the pods. In this case helm3 status is wrong.

推荐答案

请勿运行 helm delete 命令.仍然使用 2to3 插件使用命令:

Don't run the helm delete command. Still use the 2to3 plugin using the command:

$ helm3 2to3 cleanup --name <release_name>

( 是版本2,helm3 是版本3)

(helm is version 2 and helm3 is version 3)

使用 helm list 检查helm版本,该应用程序/版本应已消失.使用 helm3 list 检查helm3版本,该应用程序/版本仍应存在.

Check the helm release with helm list, the app/release should be gone. Check the helm3 release with helm3 list, the app/release should still be there.

这篇关于Helm 2to3迁移,成功迁移后是否要运行Helm Delete?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆