CNI version will roll back to 1.3.0 after upgrade to 1.40

lfaws commented 5 years ago

The CNI version will roll back to 1.3.0 after upgrading to 1.3.3 or 1.4.0

pahud commented 5 years ago

Can you tell more details about it? How to reproduce this issue?

lfaws commented 5 years ago

I upgraded the CNI plugin followed this link:https://docs.aws.amazon.com/zh_cn/eks/latest/userguide/cni-upgrades.html.

It looks like the plugin was successfully upgraded from 1.3.0 to 1.3.3 temporarily. However when you check the version again, the version will be rollback to the previous one.

This also applied to upgrade to 1.4.0 follow the link: https://github.com/nwcdlabs/kops-cn/issues/67 it will success at the beginning, but will roll back to 1.3.0 after couple of minutes.

Any suggestion or guidance will be appreciated.

pahud commented 5 years ago

https://docs.aws.amazon.com/zh_cn/eks/latest/userguide/cni-upgrades.html. 这个文件提供的方法只适合Amazon EKS，不一定适合kops

根据上游这个目录看来，kops 1.11目前只支持到1.3.0 AWS VPC CNI

master branch 25天前开始支持1.3.3，但注意，master branch不一定相容目前正在运行的kops，而且merge进master不表示它已经稳定。

此外，当AWS VPC CNI发布最新release的时候，不表示它就一定可以稳定运行在当前的Amazon EKS或当前的Kops，除非Amazon EKS与Kops官方文件提供了做法，否则应该视为未经测试且不建议的配置。

https://github.com/kubernetes/kops/tree/master/upup/models/cloudup/resources/addons/networking.amazon-vpc-routed-eni

而最新1.4.0完全没有在上游kops里面看到建议的更新方式或讨论。建议到上游kops开一个issue询问看看上游开发者是否建议升级。

kops版本相对保守很多，有可能并没有很好支持AWS VPC CNI 1.4.0

nwcdheap / kops-cn

CNI version will roll back to 1.3.0 after upgrade to 1.40 #71