Ingress resources.

[prom3theu5]

🚀 Introduce ingress Generation

As an engineer I'd like to have an interactive menu that can allow setup of ingress for select services from the aspire manifest.

✔ Goals

• [ ] allow deploy of ingress controller (docker desktop doesn't have one by default)
• [ ] allow selection of exposables
• [ ] allow definition of hosts and tls secrets.

🧰 technical

Offer support for nginx initially, then maybe allow deployment of traefik, yarp?

[mohdali]

I would be interested in this. My use case involves handling session affinity for SignalR communications.

Is there any ongoing work on this? Would be happy to try to contribute.

[dotnetian]

Any updates?

[prom3theu5]

Not yet unfortunately in terms of ingress. We now have the aspirate run command which will launch anything with a public http endpoint as a NodePort and give you direct access etc,

The problem is its not going to work well locally for actual ingress. Docker Desktop doesn't come with an ingress controller, and while I could offer deployment of something like nginx, yarp of traefik, without a valid domain (and without patching a users hosts file which would require admin privileges) you'd require app changes to set base path etc as you'd be stuck exposing ingress hosts as things like http://localhost/aspire-dashboard http://localhost/apiservice

We can definitely implement for remote clusters though, as long as a domain is available to be used. Then comes the need to maybe also add cert-manager, for certificate generation, and that brings even more questions as we'd have to have the option to do things like use lets encrypt, zerossl, cloudflare dns verification etc

[prom3theu5]

I would be interested in this. My use case involves handling session affinity for SignalR communications.

Is there any ongoing work on this? Would be happy to try to contribute.

Any input or contributions are always welcomed 😄

[dotnetian]

@prom3theu5 is Aspir8 currently deployable considering that public endpoint configuration is still not done?

If yes, could you please provide a brief explanation of how is that done?

[prom3theu5]

Aspirate isn't deployable by itself, its a cli tool but the manifests it generates - Yeah absolutely

You'd either manually add it to the generated kustomize manifests, apply as patches or edit the generated helm chart to add in your extras / ingress rules etc if you have an ingress controller running in your cluster.

Or if using aspirate run it'll expose public endpoints as node ports and produce a table output with all the addresses

[EwoutdBoer]

nginx to start sounds like a good plan. I would like Yarp support later as well to keep all in the Microsoft stack