Notary-k8s
Platform:
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/edge | 22 | 08 Oct 2024 | |
| latest/edge | 7 | 13 Sep 2024 | |
| latest/edge | 6 | 13 Sep 2024 | |
| latest/edge | 5 | 13 Sep 2024 | |
| 1/stable | 64 | 15 Oct 2026 | |
| 1/candidate | 64 | 15 Oct 2026 | |
| 1/beta | 64 | 15 Oct 2026 | |
| 1/edge | 65 | 16 Oct 2026 | |
| 0/candidate | 24 | 11 Oct 2024 | |
| 0/beta | 24 | 11 Oct 2024 | |
| 0/edge | 60 | 07 Oct 2026 | |
| 0/edge | 51 | 02 Jun 2025 |
juju deploy notary-k8s --channel 1/stable
-
email | string
Account email for Let's Encrypt (or the chosen ACME server). Used to sign CSRs arriving on the acme-certificates integration.
-
external-hostname | string
Set the external hostname that Notary expects to be accessed by all parties. This will be used as
- the subject in the generated self-signed certificates if none are provided,
- the hostname in the CRLDistributionPoint extension in all certificates created by Notary,
- the hostname in the OIDC integration used by notary.
-
plugin | string
The LEGO DNS plugin (dns_provider) used to solve DNS-01 challenges. Choose from https://go-acme.github.io/lego/dns
-
plugin-config-secret-id | string
The ID of the Juju user secret holding the credentials required by the selected LEGO DNS plugin. Secret keys are the plugin's environment variable names in lowercase with dashes instead of underscores, per the LEGO documentation (https://go-acme.github.io/lego/dns). For example, the route53 plugin needs aws-access-key-id and aws-secret-access-key, which are passed to Notary as AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
-
server | string
ACME server directory URL. For example: https://acme-v02.api.letsencrypt.org/directory