juju expose conflicts with ingress in podspec potentially

Bug #1854123 reported by Yang Kelvin Liu
10
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 :

This has the ability to take down a production deployment, by removing the ingress created by the charm - see https://bugs.launchpad.net/juju/+bug/1884674 for further details.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.