Comment 1 for bug 1889703
Revision history for this message
| John A Meinel (jameinel) wrote Re: k8s ingress doesn't seem to support non-web services | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
We dug into this a bit on our end, and the track led us down:
https:/
Really only defines ways of exposing HTTP workloads. There doesn't seem to be anything in Ingress rules that would expose alternative ports/sockets like UDP for Bind.
That said, Nginx is one of the most common ingress controllers, and it is happy to support configuration that exposes raw TCP or UDP:
https:/
Do we know if there are plans inside K8s to update the Ingress definitions to expose services other-than-http?
In the meantime, could we have our Nginx ingress controller charm have a 'expose' sort of relation, that you could then relate your Bind charm to Nginx and have it ask for Nginx to get the extra configuration?