juju expose could allow exposing to a specific CIDR/IP
Bug #1401358 reported by
Michael Nelson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
Medium
|
Unassigned |
Bug Description
This is pretty specific to a certain situation, but in case there are other situations where it would also be useful: I need to expose a service just to a specific IP/CIDR. Currently I can do:
juju expose postgresql-service
which will update the secgroup to allow anything to access it and then manually update the secgroup. What I'd like to do is:
juju expose postgresql-service --limit-to 1.2.3.4/24
or similar.
(The situation I have is a deployment where the database exists on metal, but when testing the deployment, I'm creating a postgresql service in a separate environment and exposing it to the application service only by manually updating the secgroup.)
tags: | added: expose feature |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
How about adding to the charm: open-port 0-65535/tcp
?
As we implement the ability to deploy services into juju network spaces, this and similar UX issues should improve a lot.