Hydra
- Identity Charmers
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 276 | 24 Apr 2024 | |
| latest/edge | 322 | Yesterday | |
| 0.3/edge | 320 | 07 Nov 2024 | |
| 0.2/stable | 285 | 26 Jun 2024 | |
| 0.2/edge | 285 | 09 May 2024 | |
| 0.1/edge | 270 | 24 Nov 2023 |
juju deploy hydra --channel 0.1/edge
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Hydra Charm Security
This document provides cryptographic documentation for the Hydra charm. Its purpose is to track the exposure of charm code to cryptographic attack vectors.
What is not included in this document and regarded as out of scope:
- Workload code (refer to the workloads’ cryptographic documentation).
- Data at rest encryption.
Sensitive Data Exchange
The charm relies on Juju secrets:
- To pass Hydra client secret that is used to access Hydra API.
- To pass Hydra system secret that is used to encrypt Hydra’s database.
Github secrets are used during development, build, test and deploy phases:
- To get Charmcraft credentials that are used to interact with Charmhub.
- To get a Github token that is used to interact with Github API.
Cryptographic tech and packages in use
Hydra charm uses the following cryptography packages:
- Python secrets built-in library is used to generate random strings for the cookie and database encryption/signing.