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
We use kubernetes and different nodes can have different architectures (arm/amd). We have to build a separate docker image for each of these architectures, so the sentry build id ends up being different and the contenthash changes between the two. When there is a pod on each architecture the different contenthashes cause 404's and errors.
Is there a way to force the uuid to be calculated based on the release and not per-build?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We use kubernetes and different nodes can have different architectures (arm/amd). We have to build a separate docker image for each of these architectures, so the sentry build id ends up being different and the contenthash changes between the two. When there is a pod on each architecture the different contenthashes cause 404's and errors.
Is there a way to force the uuid to be calculated based on the release and not per-build?
All reactions