Please help us help you and fill where relevant:
Your LimeSurvey version: 6.x.x
Own server or LimeSurvey hosting:
Survey theme/template:
==================When running LimeSurvey with multiple pods (2+) and , static assets are published under hashed folders, e.g.:/tmp/assets/61f5ab8b/jquery-ui.min.css
/tmp/assets/adedf5c9/css/font-awesome.min.css
/tmp/assets/379ee63f/ibm-sans.css
...

Intermittently we get 404 errors for those URLs. This seems to happen when the load balancer routes a user from pod A to pod B (or after a pod restart) — each pod has a different /tmp/assets content, so the hashed directory names don’t always exist on the other pod.
 What we want

• Keep
  Code:

  debug=0

  (production).
• Avoid 404s in multi-pod environment.
• Ideally have both pods serve the same asset paths (no per-pod hash differences), or an officially recommended way to make asset publishing deterministic/shared in production.
  
  Is there an officially supported way in LimeSurvey to run with
  Code:

  debug=0

  and disable AssetManager’s hashing, or to make hashed output deterministic and identical across pods?

Unsure, but maybe you can try different assetsversionnumber for each pod ? 
or customassetversionnumber  github.com/LimeSurvey/LimeSurvey/blob/88...ts.php#L96C10-L96C34  
You can set it in config.php file in the config array.
github.com/LimeSurvey/LimeSurvey/blob/88...on.php#L19C10-L19C29

Else : try use_asset_manager to false. 
www.limesurvey.org/manual/Optional_setti...opment_and_debugging