---
title: Beta versions
---

You can test upcoming authentik versions, including major new features that are in "Beta release", by switching to the _next_ images. It is recommended to upgrade to the latest stable release before upgrading to Beta images. It is always possible to upgrade from the Beta to the next stable release.

:::warning
Downgrading from the Beta is not supported. It is recommended to take a backup before upgrading, or test Beta versions on a separate install. Upgrading from Beta versions to the next release is usually possible, however also not supported.
:::

import TabItem from "@theme/TabItem";
import Tabs from "@theme/Tabs";

<Tabs
  defaultValue="docker-compose"
  values={[
    {label: 'Docker Compose', value: 'docker-compose'},
    {label: 'Kubernetes', value: 'kubernetes'},
  ]}
  groupId="platform">
  <TabItem value="docker-compose">
Add the following block to your `.env` file:

```shell
AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-next
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
```

Next, run the upgrade commands below.

  </TabItem>

  <TabItem value="kubernetes">
Add the following block to your `values.yml` file:

```yaml
authentik:
    outposts:
        container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
image:
    repository: ghcr.io/goauthentik/dev-server
    tag: gh-next
    # pullPolicy: Always to ensure you always get the latest version
    pullPolicy: Always
```

Next, run the upgrade commands below.

  </TabItem>
</Tabs>

<Tabs
  defaultValue="docker-compose"
  values={[
    {label: 'Docker Compose', value: 'docker-compose'},
    {label: 'Kubernetes', value: 'kubernetes'},
  ]}
  groupId="platform">
  <TabItem value="docker-compose">

```shell
docker compose pull
docker compose up -d
```

  </TabItem>

  <TabItem value="kubernetes">

```shell
helm repo update
helm upgrade authentik authentik/authentik -f values.yaml
```

  </TabItem>

</Tabs>

:::info
If you are upgrading from an older Beta release to the most recent Beta release, you might need to run `kubectl rollout restart deployment`, because Helm needs to recreate the pods in order to pick up the new image (the tag doesn't change).
:::

To verify whether the upgrade was successful, go to your Admin panel and navigate to the Overview dashboard. There, you can check the version number to ensure that you are using the Beta version you intended.
