Temporarily replaced a Lambda Function URL with a regional API Gateway route to fit the pinned provider. The endpoint was later removed when the final review required the completion receiver to remain inside Kubernetes.
- What worked
- It offered a provider-compatible, narrowly scoped invocation path for the temporary serverless design.
- What got in the way
- Although technically viable, it expanded application processing outside the mandated cluster boundary.
