| 2020-07-31 02:25:28 |
Barry Price |
bug |
|
|
added bug |
| 2020-07-31 02:52:08 |
Ian Booth |
juju: milestone |
|
2.8.3 |
|
| 2020-07-31 02:52:13 |
Ian Booth |
juju: importance |
Undecided |
High |
|
| 2020-07-31 02:52:17 |
Ian Booth |
juju: status |
New |
Triaged |
|
| 2020-09-14 05:15:54 |
Barry Price |
summary |
k8s ingress doesn't seem to support non-web services |
Juju expose on k8s doesn't seem to support non-web services |
|
| 2020-09-14 05:16:14 |
Barry Price |
description |
I can write a charm to deploy a network service running on an arbitrary TCP/UDP port, the pods deploy correctly and the service works fine on the individual units.
But Juju doesn't seem to be able to set up an ingress for us in this use case.
Even with our ports defined correctly in the pod spec as e.g. TCP/123 or UDP/456, running 'juju expose' seems to ignore them and instead creates an ingress for TCP/80. |
I can write a charm to deploy a network service running on an arbitrary TCP/UDP port, the pods deploy correctly and the service works fine on the individual units.
But Juju doesn't seem to be able to set up an ingress for us in this use case.
Even with our service ports defined correctly in the pod spec as e.g. TCP/123 or UDP/456, running 'juju expose' seems to ignore them and instead creates an ingress for TCP/80. |
|
| 2020-09-14 21:42:38 |
John A Meinel |
juju: milestone |
2.8.3 |
|
|
| 2021-06-04 03:23:13 |
Barry Price |
description |
I can write a charm to deploy a network service running on an arbitrary TCP/UDP port, the pods deploy correctly and the service works fine on the individual units.
But Juju doesn't seem to be able to set up an ingress for us in this use case.
Even with our service ports defined correctly in the pod spec as e.g. TCP/123 or UDP/456, running 'juju expose' seems to ignore them and instead creates an ingress for TCP/80. |
I can write a charm to deploy a network service running on an arbitrary TCP/UDP port, the pods deploy correctly and the service works fine on the individual units.
But Juju doesn't seem to be able to set up a Service for us in this use case.
Even with our service ports defined correctly in the pod spec as e.g. TCP/123 or UDP/456, running 'juju expose' seems to ignore them and instead creates an Ingress for TCP/80. |
|
