---
title: Charmhub | Deploy Tempest K8S using Charmhub - The Open Operator Collection
description: Deploy the latest version of Tempest K8S as a Kubernetes Operator on
  any cloud.
url: https://charmhub.io/tempest-k8s/configurations
---

# Tempest K8S

[OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

* [OpenStack Charmers](https://charmhub.io/publisher/openstack-charmers "View all packages from OpenStack Charmers")

Platform:

2024.1/stable 060d2288

```
juju deploy tempest-k8s --channel 2024.1/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

* [region](https://charmhub.io/tempest-k8s/configurations#region)
* [roles](https://charmhub.io/tempest-k8s/configurations#roles)
* [schedule](https://charmhub.io/tempest-k8s/configurations#schedule)
* [tempest-accounts-count](https://charmhub.io/tempest-k8s/configurations#tempest-accounts-count)
* [tempest-concurrency](https://charmhub.io/tempest-k8s/configurations#tempest-concurrency)

[Learn about configurations >](https://juju.is/docs/juju/configuration#heading--application-configuration)

* 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 crontab` for 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.