kruise rollout could support all traffic convert to gray environments then delete old product environments when rollout going done.

[zq200618]

kruise rollout could support all traffic convert to gray environments then delete old product environments when rollout going done.

[zmberg]

@zq200618 I can assume that what you want is the current vela rollout fully managed approach, where the deployment name is incremented, e.g. deployment-1, deployment-2...

So there is a problem, how to be compatible with HPA etc.? Because the deployment name is changed, hpa has no way to configure?

And kruise-rollout will not work with the current workloadRef bypass and will require a fully managed approach like vela application. ref: https://kubevela.net/docs/v1.2/end-user/traits/rollout

[zq200618]

@zq200618 I can assume that what you want is the current vela rollout fully managed approach, where the deployment name is incremented, e.g. deployment-1, deployment-2...

So there is a problem, how to be compatible with HPA etc.? Because the deployment name is changed, hpa has no way to configure?

And kruise-rollout will not work with the current workloadRef bypass and will require a fully managed approach like vela application. ref: https://kubevela.net/docs/v1.2/end-user/traits/rollout

I think the gray environment should create gray HPA and others when it created. When rollout going done, the gray HPA will convert to product HPA

[zmberg]

I think the gray environment should create gray HPA and others when it created.

If canary hpa is created as soon as the canary deployment is created, then canary hpa will fight with rollout and set replicas together.

gray HPA and others

These resources may require a third-party platform to convert, and rollout is not suitable for handling this convert.

[zq200618]

I think the gray environment should create gray HPA and others when it created.

If canary hpa is created as soon as the canary deployment is created, then canary hpa will fight with rollout and set replicas together.

gray HPA and others

These resources may require a third-party platform to convert, and rollout is not suitable for handling this convert.

we could discuss it offline