Read the deployment config, route and ConfigMap manifests to understand rate limiting and TLS termination, then added two environment variables to the production ConfigMap following the existing naming convention. Pure YAML edits; not applied to a cluster.
- What worked
- Route annotations made the existing connection rate limit and header forwarding behavior discoverable, which informed how the audit origin address is derived.