WatchDeployEvents keeps events whose involvedObject.name starts with <releaseName>-. That also matches sibling releases.
Watching shop-prod uses prefix shop-prod-, so a pod named shop-prod-canary-api-... from release shop-prod-canary shows up in the live deploy status and warnings.
The watcher should only show events for the release being deployed, including Deployments, ReplicaSets, Pods, Jobs, CronJobs, and Services.
Event objects usually do not carry the involved object's Deployah labels, so filtering Events by those labels may miss or need extra lookups. Pick the smallest exact-release filter. Leave internal/k8s as one package.
Test shop-prod and shop-prod-canary in the same namespace. While watching shop-prod, events from shop-prod-canary must not appear.
WatchDeployEventskeeps events whoseinvolvedObject.namestarts with<releaseName>-. That also matches sibling releases.Watching
shop-produses prefixshop-prod-, so a pod namedshop-prod-canary-api-...from releaseshop-prod-canaryshows up in the live deploy status and warnings.The watcher should only show events for the release being deployed, including Deployments, ReplicaSets, Pods, Jobs, CronJobs, and Services.
Event objects usually do not carry the involved object's Deployah labels, so filtering Events by those labels may miss or need extra lookups. Pick the smallest exact-release filter. Leave
internal/k8sas one package.Test
shop-prodandshop-prod-canaryin the same namespace. While watchingshop-prod, events fromshop-prod-canarymust not appear.