-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support patchPodTemplateMetadata when enableExtraWorkloadForCanary = false #247
Comments
what do you need for the extra label of canary pods, if you just want to find the canary pods, you can set order id (rollouts.kruise.io/rollout-id) in workload and the pod will be patch with batch id(rollouts.kruise.io/rollout-batch-id) |
ok thanks. Due to architectural historical reasons, our service discovery distinguishes canary pods by identifying the label of the pod (version=canary). And our PaaS Release Platform supports choosing whether to enableExtraWorkloadForCanary before release, which requires a unified method to label pod (use rollouts.kruise.io/rollout-id uniformly or use patchPodTemplateMetadata uniformly.). Here are one questions to confirm: Will rollouts.kruise.io/rollout-id take effect when enableExtraWorkloadForCanary=true? |
rollouts.kruise.io/rollout-id currently only works for case enableExtraWorkloadForCanary=true. |
@PersistentJZH can you attend the biweekly meeting tonight, we can have a discuss about the support of patchPodTemplateMetadata when enableExtraWorkloadForCanary = false |
sure, I will attend on time. thanks. |
Hi masters, Currently patchPodTemplateMetadata will only take effect when enableExtraWorkloadForCanary = true. Whether to consider also supporting patchPodTemplateMetadata when enableExtraWorkloadForCanary = false.
Background: We use kruise rollout for canary release, and distinguish canary pods through pod labels. For some reason, we need to set enableExtraWorkloadForCanary to false, so we want to add some labels to the canary pod through patchPodTemplateMetadata in this case.
The text was updated successfully, but these errors were encountered: