Matthew Alberts

Hi @DiegoLelis the container images need to be built specific to architecture. When a pod requests its image, it passes forward the architecture, allowing for seemless use of multi-architecture instances...

@tonyxiao feels like a dup or belongs under #32?

This is the remainder of the issue reported by #10

That’s correct, path based routing isn’t supported. Rather that ignoring the path and establishing a tunnel base on host:port, in the 0.6.x line I decided to explicitly error on t...

@tanner-bruce Your best option to get both the behavior you need, is use `cloudflared` as a side-car to a proxy that supports path based routing. For example: - ingress-nginx (nginx)...

I'd definitely like to support gRPC, I just haven't tested and debugged a gRPC service behind a tunnel yet (and it will largely depend on what argo-tunnel provides, this is...

@Maxpain177 the tunnel controller doesn't expose a way to configure sticky sessions, though you are able to configure session affinity as part of the load-balancer - [LoadBalancer Setup](https://support.cloudflare.com/hc/en-us/articles/115000081911-Tutorial-How-to-Set-Up-Load-Balancing-Intelligent-Failover-on-Cloudflare) - [LoadBalancer...

@Maxpain177 (sorry for the delay was digging around/investigating/fixing issues). Correct, the current version of the ingress controller maps a "tunnel" to a service (specifically `namespace.name:port`). I that model, you're left...

@Maxpain177 correct. As i try to draft up changes for 0.6.x I can start looking at that. An easy way around the restrictions (and maybe a better model than a...

@Maxpain177 To ensure you don't get blocked or sad, I thought I'd update the issue. I don't have plans to correct the ingress-controller in the short-term (or even mid-term). Given...