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
The arm64 variant had its own `app.kubernetes.io/name`, so the chart made a
second Service and a second PodDisruptionBudget for it. The HTTPRoute backs
only the amd64 Service, so the arm64 pods never received traffic.
Both architectures now keep the same name label. arm64 adds
`app.kubernetes.io/component: arm64`, which keeps its Deployment selector
unique. One Service and one budget now cover the pods of both, and the load
balancer sends traffic to both.
This makes the architecture difference one line in the selector helper, so
the per-architecture copies in the Service and the budget templates are
deleted, and `lago-rails.architecture.labels` is deleted. That helper was a
copy of `lago-rails.labels` with one line different. All templates use the
common helper again.
The amd64 output does not change.
CAUTION: `spec.selector` of a Deployment is immutable. Delete each live
`*-arm64` Deployment one time before the next sync.
0 commit comments