Tempest K8S
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 2025.1/edge | 183 | 29 Mar 2026 | |
| 2024.1/stable | 177 | 24 Mar 2026 | |
| 2024.1/stable | 62 | 30 Apr 2025 | |
| 2024.1/candidate | 177 | 23 Mar 2026 | |
| 2024.1/candidate | 62 | 16 Jan 2025 | |
| 2024.1/beta | 180 | 27 Mar 2026 | |
| 2024.1/beta | 62 | 22 Nov 2024 | |
| 2024.1/edge | 184 | 29 Mar 2026 | |
| 2024.1/edge | 62 | 08 Oct 2024 | |
| 2023.2/candidate | 23 | 09 Apr 2024 | |
| 2023.2/beta | 23 | 09 Apr 2024 | |
| 2023.2/edge | 30 | 06 May 2024 |
juju deploy tempest-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:
-
region | string
Default: RegionOne
Name of the OpenStack region
-
roles | string
Default: storage,compute,control
A comma-separated list of Sunbeam node roles to be used for enabling tempest tests. Removing a role from the list will disable tempest tests relating to that role. Valid roles are: storage, compute, control.
-
schedule | string
Default: 0 */1 * * *
The cron schedule expression to define when to run tempest periodic checks.
The value will only take effect when 'logging' relation is joined. Otherwise, regardless of the value set, periodic checks are disabled.
By default, tests will run every hour. When the value is set to empty, periodic checks will be disabled.
The cron implementation used is Vixie Cron, installed from Ubuntu main. For help with expressions, see
man 5 crontabfor Vixie Cron, or visit https://crontab.guru/ .The schedule should not result in tempest running more than once every 15 minutes.
Example expressions:
"*/30 * * * *" every 30 minutes "5 2 * * *" at 2:05am every day "5 2 * * mon" at 2:05am every Monday
-
tempest-accounts-count | int
Default: 8
Number of tempest accounts for testing.
It's desirable to have more accounts than the concurrency so it can be set to a value higher than the max concurrency (see get_tempest_concurrency()) while remaining a relatively small number.
This also helps mitigate effects of credential locks not being released (LP: #2052752).
-
tempest-concurrency | int
Default: 4
Upper bound for test concurrency. The effective concurrency is the minimum of this value and the number of CPU cores available to the container.