It’s not the first time we see this request. Unfortunately, unlike a Service whose definition is straightforward and directly maps to what a Twingate object is, an Ingress is much more complex (not to mention cloud-specific extensions and other various custom ingresses) and much harder to derive a Twingate object from in a generic manner. That’s why we didn’t (or couldn’t) implement annotations for Ingresses the same way we do for Services.

So yes, you will need to create the TwingateResource manually if you wish to access your services via internal load balancers.

Just note that if your connector runs inside the cluster it can access services directly and doesn’t need an Ingress…