You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
旧版本 csi 生成的 pod 没有做任何配置修改,仍然会被升级
原因是 旧版的 csi 生成的 mount pod 的配置是 csi 拼成的(有一些信息拿不到),没有记录在 secret 里,然后升级的时候拿拼凑出来的配置和现有的做对比,主要是拿配置 setting 算出一个 hash 做对比,所以会不准。现在新的版本里是把 setting 存在 secret 里,这样每次都是拿上一次生成的配置。
拿旧版本生成的 pod 前两次升级会有这个问题,第三次就固定了 What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
JuiceFS CSI Driver version (which image tag did your CSI Driver use):
Kubernetes version (e.g. kubectl version):
Object storage (cloud provider and region):
Metadata engine info (version, cloud provider managed or self maintained):
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
Others:
The text was updated successfully, but these errors were encountered:
What happened:
旧版本 csi 生成的 pod 没有做任何配置修改,仍然会被升级
原因是 旧版的 csi 生成的 mount pod 的配置是 csi 拼成的(有一些信息拿不到),没有记录在 secret 里,然后升级的时候拿拼凑出来的配置和现有的做对比,主要是拿配置 setting 算出一个 hash 做对比,所以会不准。现在新的版本里是把 setting 存在 secret 里,这样每次都是拿上一次生成的配置。
拿旧版本生成的 pod 前两次升级会有这个问题,第三次就固定了
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: