[RFE] support tls-certificates relation
Bug #1780542 reported by
Dmitrii Shcherbakov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Percona Cluster Charm |
Triaged
|
Wishlist
|
Unassigned | ||
OpenStack RabbitMQ Server Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Having certificates provided via vault or easyrsa would be good to have (for in-cluster TLS and client access).
Vault's dependence on a storage backend and storage backend's dependency on vault as a cert provider does not make it easy. One potential way to solve it would be collocation of Percona and vault "initial coordinator" units on the same logical machine and Unix socket communication for initial storage with one active unit before clustering but this is non-trivial too.
Either way, the need for this workflow exists.
Changed in charm-percona-cluster: | |
status: | New → Triaged |
Changed in charm-rabbitmq-server: | |
status: | New → Triaged |
Changed in charm-percona-cluster: | |
importance: | Undecided → Wishlist |
Changed in charm-rabbitmq-server: | |
importance: | Undecided → Wishlist |
To post a comment you must log in.