Promoting a Service's Ingress to a New Environment

Your service already has working ingress in one environment, for example
staging, and you now need the same service reachable in another, for example
production. The safest approach is to copy the configuration that already
works rather than write a new one.

Steps

1. Open the working environment in SVIEW and go to the service's Component
   configuration.
2. Copy the whole ingress block.
3. Open the same service's Component in the target environment and paste the
   block in.
4. Change only the hostname to the one for the new environment.
5. Save, and wait for the deployment to finish.

Keep every other setting — annotations, paths, and TLS configuration — exactly
as it is in the working environment. Re-deriving a working configuration from
scratch is the usual source of a typo in a part that should have stayed
identical.

Verify it worked

Once the deployment completes, request the new hostname over HTTPS and confirm
that it resolves, that the certificate is valid, and that the response comes
from your service.

Remember that the new hostname needs a DNS record pointing at the environment's
ingress before it will resolve. See
Ingress, Custom Domains and TLS
for the DNS and certificate steps.

Related articles

• Ingress, Custom Domains and TLS
• Troubleshooting
• Environments