Automate exposing arbitrary ports
Bug #1842104 reported by
Andrea Ieri
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes Worker Charm |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
As described in the charm documentation under 'known limitations', there is currently no automation for port exposure when using NodePort type networking.
It would be useful to have a charm config specifying a list of ports that need to be opened (e.g. to setup an external ingress controller): all the charm would have to do is loop through the list and open/close ports as necessary.
Revision history for this message
| Pedro Guimarães (pguimaraes) wrote | #1 |
| Changed in charm-kubernetes-worker: | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Pedro Guimarães (pguimaraes) |
| Changed in charm-kubernetes-worker: | |
| assignee: | Pedro Guimarães (pguimaraes) → nobody |
| status: | In Progress → Confirmed |
Revision history for this message
| Andrea Ieri (aieri) wrote | #2 |
To post a comment you must log in.
As LP #1427770 is marked as "Won't Fix", we can easily manage that via config using commands open/close-port and opened-ports on Juju.
PR proposed to solve this issue:
https:/