Self Signed X.509 Certificates
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 264 | 11 Mar 2025 | |
| latest/stable | 265 | 11 Mar 2025 | |
| latest/candidate | 265 | 10 Mar 2025 | |
| latest/candidate | 264 | 10 Mar 2025 | |
| latest/beta | 265 | 10 Mar 2025 | |
| latest/beta | 264 | 10 Mar 2025 | |
| latest/edge | 419 | 25 Oct 2025 | |
| latest/edge | 418 | 25 Oct 2025 | |
| 1/stable | 317 | 10 Jun 2025 | |
| 1/stable | 262 | 11 Mar 2025 | |
| 1/candidate | 317 | 10 Jun 2025 | |
| 1/candidate | 262 | 10 Mar 2025 | |
| 1/beta | 396 | 15 Oct 2025 | |
| 1/beta | 262 | 10 Mar 2025 | |
| 1/edge | 417 | 23 Oct 2025 | |
| 1/edge | 416 | 23 Oct 2025 | |
| 1/edge | 327 | 31 Jul 2025 | |
| 1/edge | 247 | 03 Mar 2025 |
juju deploy self-signed-certificates --channel 1/edge
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
24.04
22.04
self-signed-certificates Tracks and Compatibility
This document seeks to clarify which track should be used when deploying a new self-signed-certificates charm.
The names of the tracks can be confusing.
- The
latesttrack is actually a legacy track that should no longer be used. Charms should migrate to the1/stabletrack when possible. - The
1track is the current track and should be used for all new deployments.
Compatiblity with Requirer Charms
The latest track of the charm is not compatible with requirer charms that use:
- tls-certificates-interface
V4, APP mode - certificate-transfer-interface
V1
Juju Version Compatibility
The charm is able to run on any cloud and substrate that Juju supports, be it a k8s container or a VM.
| Charmhub Track | Juju Version Compatibility | Recommended for new deployments |
|---|---|---|
| 1/stable | Juju 3.1+ | Yes |