juju expose conflicts with ingress in podspec potentially
Bug #1854123 reported by
Yang Kelvin Liu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
If the charm already provided ingress for app svc itself in the pod spec, should we touch/overwrite that spec at all if the user run `juju expose` or just reject and errors out for the cmd?
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in juju: | |
| importance: | Wishlist → High |
Revision history for this message
| Joel Sing (jsing) wrote | #1 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | High → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This has the ability to take down a production deployment, by removing the ingress created by the charm - see https:/