Add action to create new certs against CA
Bug #1809378 reported by
Tim Van Steenburgh
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| EasyRSA Charm |
New
|
Undecided
|
Unassigned | ||
Bug Description
Opened by marcoceppi on 2017-10-11 18:47:24+00:00 at https:/
-------
When plugging in solutions that are not Juju deployed, IE: docker registry, it'd be nice to have an action that produced a cert by the operator against the EasyRSA CA.
=======
Comment created by MadWombat on 2018-05-02 17:58:01+00:00
I think this ability might be useful in other use cases as well. For example to use client certs to grant access to the API. Currently it is unclear how to do that with a juju managed kube cluster.
To post a comment you must log in.
