· Infrastructure · 5 min read
Edge routing and TLS automation without the ingress tax
By Ethan Cole, Co-Founder & CTO
Most teams only want HTTPS in front of their web service and clean connection draining during a deploy. They should not have to maintain an ingress controller to get it.
Every small infrastructure team hits the same detour right before launch: the application containers are ready, and then three days vanish into ingress annotations, cert-manager CRDs, DNS challenge records, and mismatched idle timeouts.
When a deploy stalls or a certificate renewal fails quietly, nobody blames the container image. They end up debugging YAML flags between a cloud load balancer, an ingress controller, and the service port underneath.
We built Nimbus edge routing around a narrower contract. Point a domain at your service, declare the listening port and health path, and let the platform handle certificate issuance, renewal, and TLS termination automatically.
During a rolling update, new containers must pass readiness checks before edge routing shifts traffic, and existing keep-alive connections drain before old replicas exit. You do not need custom annotations just to avoid dropped requests on deploy.
Underneath, the routing layer still maps cleanly to standard Kubernetes Services in your account. You keep clear failure visibility and full portability, without keeping ingress plumbing on your sprint board.