Main Service always uses the Pod port in a K8s Charm
Bug #1902000 reported by
Dominik Fleischmann
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Yang Kelvin Liu | ||
Bug Description
The Kubernetes Service that a K8s Charm creates will use the same containerPort that has been defined for the Pod.
There should be a way of configuring different ports as this direct mapping is not always intended in K8s applications.
The current Workaround is creating a second Service that uses a different port. But this is not an ideal solution.
For further context please check this Discourse thread:
https:/
| Changed in juju: | |
| milestone: | none → 3.0.0 |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 3.0.0 → 3.0.1 |
| Changed in juju: | |
| milestone: | 3.0.1 → 3.0.2 |
| Changed in juju: | |
| milestone: | 3.0.2 → 3.0.3 |
| Changed in juju: | |
| assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
| Changed in juju: | |
| milestone: | 3.0.3 → 3.0.4 |
To post a comment you must log in.
