Documentation

Upgrade InfluxDB Clustered

Use Kubernetes to upgrade your InfluxDB Clustered version. The upgrade is carried out using in-place updates, ensuring minimal downtime. InfluxDB Clustered versioning is defined in the AppInstance CustomResourceDefinition (CRD) in your myinfluxdb.yml.

InfluxDB Clustered does not support downgrading. If you encounter an issue after upgrading, contact InfluxData support.

Version format

InfluxDB Clustered uses the YYYYMMDD-BUILD_NUMBER version format. For example, a version created on January 1, 2024 would have a version number similar to the following:

20240101-863513

Upgrade your InfluxDB Clustered version

  1. Identify your current InfluxDB Clustered package version
  2. Identify the version to upgrade to
  3. Update your image to use a new package version
  4. Apply the updated image

Identify your current InfluxDB Clustered package version

Use the following command to return the image Kubernetes uses to build your InfluxDB cluster:

kubectl get appinstances.kubecfg.dev influxdb -n influxdb -o jsonpath='{.spec.package.image}'

The package version number is at the end of the returned string (after influxdb:):

us-docker.pkg.dev/influxdb2-artifacts/clustered/influxdb:PACKAGE_VERSION

Identify the version to upgrade to

All available InfluxDB Clustered package versions are provided in the InfluxDB Clustered release notes. Find the package version you want to upgrade to and copy the version number.

Checkpoint releases

Some InfluxDB Clustered releases are checkpoint releases that introduce a breaking change to an InfluxDB component. Checkpoint releases are only made when absolutely necessary and are clearly identified in the InfluxDB Clustered release notes.

When upgrading, always upgrade to each checkpoint release first, before proceeding to newer versions.

Upgrade to checkpoint releases first

Upgrading past a checkpoint release without first upgrading to it may result in corrupt or lost data.

View checkpoint release upgrade example

Update your image to use a new package version

In your myinfluxdb.yml, update the package version defined in spec.package.image to the version you want to upgrade to.

apiVersion: kubecfg.dev/v1alpha1
kind: AppInstance
# ...
spec:
  package:
    # ...
    image: us-docker.pkg.dev/influxdb2-artifacts/clustered/influxdb:
PACKAGE_VERSION

Replace PACKAGE_VERSION with the version number to upgrade to.

Apply the updated image

Use the following command to apply the updated image configuration and upgrade your InfluxDB Cluster:

kubectl apply \
  --filename myinfluxdb.yml \
  --namespace influxdb

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2