Support extra service names in Kubernetes charms
Bug #1887978 reported by
Kenneth Koski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu | ||
Bug Description
I have a charm called pipelines-api that is part of the Kubeflow bundle. There are other bits of Kubeflow that default to attempting to talk to the service at ml-pipeline. Right now, we solve this by kubectl apply'ing a Service called ml-pipeline that just redirects off to the pipelines-api Service, see here:
https:/
Would it be possible to support creating multiple service names for a given charm instead of manually kubectl applying an extra Service?
| Changed in juju: | |
| assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
| milestone: | none → 2.8.2 |
| status: | New → Triaged |
| status: | Triaged → In Progress |
Revision history for this message
| Yang Kelvin Liu (kelvin.liu) wrote | #1 |
| Changed in juju: | |
| importance: | Undecided → High |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/