Investigation around CLOUDWF-11331 raised question about registry-proxy and ghcr.io auth. 

{{2025-12-16T15:20:30Z registry-proxy-isv-6cc44ff576-z9ncn /app/registry-proxy[1]: {"authenticatedUser":"marckok","deployment":"isv","level":"info","msg":"Backend request completed","requestUUID":"0b9426f3-597f-48a9-8298-31316133db85","response":

{"durationMs":29,"method":"GET","status":401,"url":"https://ghcr.io/v2/"}

,"time":"2025-12-16T15:20:30.51986963Z"}}}

Based on the logs, the auth actually worked:
{{2025-12-16T15:20:30Z registry-proxy-isv-6cc44ff576-z9ncn /app/registry-proxy[1]: {"authenticatedUser":"marckok","deployment":"isv","level":"info","msg":"Backend request completed","requestUUID":"0b9426f3-597f-48a9-8298-31316133db85","response":

{"durationMs":49,"method":"GET","status":200,"url":"https://ghcr.io/token?client_id=registry-proxy\u0026scope=repository%3Astclab-inc%2Fwave-autoscale-intelligence%3Apull\u0026service=ghcr.io"}

,"time":"2025-12-16T15:20:30.569754766Z"}}}