🐛 Managed Tunnel No Ingress Rules While Starting New Replica

[garretcharp]

Describe the bug

When starting up a new replica of a managed tunnel I get the following error for a few seconds before it actually loads the config which results in 503s to requests that come in

No ingress rules were defined in provided config (if any) nor from the cli, cloudflared will return 503 for all incoming HTTP requests

To Reproduce

Create a managed tunnel with 1 host and ensure it route properly. Add a new replica and while it is starting up make sure you are spamming requests through If you manage to hit the new replica before it loads the config you will get a 503

If it's an issue with Cloudflare Tunnel: 4. Tunnel ID : f4bb698f-261f-40a0-8cab-086f06595898