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
cloneset is designed to support one and only one target revision. cloneset may have multiple intermediate revision during rollout, but provides no mechanism to control the detailed replicas distribution of each intermediate revision. currently, the most flexible way is to use multiple deployment or cloneset to support multiple revision. However, if some form of unified controlling interface over these deployment/cloneset are desired, you're welcome to share us some ideas.
我的场景是需要做全链路灰度,但是会存在多个版本,比如4个版本,然后我会根据请求头(比如x-version: v2)去路由到v2版本的pod,有没有这部分的示例可以参考
我现在的做法是增加updateStrategy.partition的数量,跟增大replicas去做多版本同时存在的,例如,我发布了V1版本,发布V2的时候,updateStrategy.partition改成2,replicas从2改成4,发布V3的时候,updateStrategy.partition改成4,replicas从4改成6,好像只能每个版本的pod数是一致的,而且好像确保不了我每个版本的pod数该多少个,有没有像我这种场景
The text was updated successfully, but these errors were encountered: