fix(storage-resize-images): kit/extension parity – kit sets no maxInstances and allows all ingress #3275

storage-resize-images kit/extension parity. Priority: medium. The kit deploys with a lower instance limit and wider ingress than the extension.

Difference

Read from a live deploy of each on a test project:

• Once fix(storage-resize-images): match the extension's Gen1 concurrency and CPU #3234 sets concurrency: 1, the kit can resize at most 100 images at once, against 3000 on the extension.
• Not tested: whether uploads past 100 in flight are delayed and redelivered, or dropped. The trigger has no retry policy.

Code

• Extension: 1st gen resource with no instance or ingress settings (extension.yaml#L56-L66).
• Kit: the trigger sets only region, bucket and memory (index.ts#L100-L107).

Resolution

• Ingress: fix(resize): match extension concurrency and ingress #3203 sets ingressSettings: "ALLOW_INTERNAL_ONLY". It also sets concurrency: 1, which overlaps with fix(storage-resize-images): match the extension's Gen1 concurrency and CPU #3234.
• Max instances: no open PR. fix(kits): match the extensions' Gen1 concurrency and ingress #3206 sets maxInstances: 500 on syncBigQuery for the same reason. A burst of more than 100 uploads would show whether the limit loses images.