Keystone K8S
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| yoga/beta | 82 | 10 Mar 2023 | |
| yoga/edge | 99 | 16 May 2023 | |
| xena/beta | 72 | 21 Nov 2022 | |
| xena/edge | 76 | 20 Jan 2023 | |
| 2025.1/edge | 339 | 12 Mar 2026 | |
| 2024.1/stable | 332 | 09 Mar 2026 | |
| 2024.1/stable | 208 | 30 Apr 2025 | |
| 2024.1/candidate | 332 | 07 Mar 2026 | |
| 2024.1/candidate | 208 | 16 Jan 2025 | |
| 2024.1/beta | 341 | Yesterday | |
| 2024.1/beta | 208 | 22 Nov 2024 | |
| 2024.1/edge | 341 | 12 Mar 2026 | |
| 2024.1/edge | 208 | 07 Oct 2024 | |
| 2023.2/stable | 148 | 06 Dec 2023 | |
| 2023.2/candidate | 169 | 05 Apr 2024 | |
| 2023.2/beta | 169 | 05 Apr 2024 | |
| 2023.2/edge | 169 | 03 Apr 2024 | |
| 2023.1/stable | 125 | 26 Sep 2023 | |
| 2023.1/candidate | 155 | 12 Jan 2024 | |
| 2023.1/beta | 155 | 10 Jan 2024 | |
| 2023.1/edge | 155 | 03 Jan 2024 |
juju deploy keystone-k8s --channel 2024.1/stable
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:
-
catalog-cache-expiration | int
Default: 60
Amount of time (in seconds) the catalog should be cached for.
-
debug | boolean
Enable debug logging.
-
dogpile-cache-expiration | int
Default: 60
Amount of time (in seconds) to cache items in the dogpile.cache. This only applies to cached methods that do not have an explicitly defined cache expiration time.
-
enable-telemetry-notifications | boolean
Enable notifications to send to telemetry.
-
identity-backend | string
Default: sql
Keystone identity backend, valid options are sql and pam
-
log-level | string
Default: WARNING
Log level (WARNING, INFO, DEBUG, ERROR)
-
region | string
Default: RegionOne
Name of the OpenStack region
-
saml-x509-keypair | secret
The SAML2 x509 certificates. This certificate is used by SAML2 for two purposes:
- Sign messages between the SP and the IDP
- Encrypt messages. This is rarely used as in the majority of cases, SAML2 traffic is sent over https. This certificate will be part of the SAML2 metadata. The secret is expected to have two keys:
{ "certificate": "contents of the certificate", "key": "contents of the key" }
You can upload the secrets by running:
juju add-secret saml-secret
certificate#file=/path/to/cert.pem
key#file=/path/to/corresponding/key juju grant-secret saml-secret keystone