Documentation

Upgrade InfluxDB Clustered

Limited availability

InfluxDB Clustered is currently only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Use Kubernetes to upgrade your InfluxDB Clustered version. InfluxDB Clustered versioning is defined in the AppInstance CustomResourceDefinition (CRD) in your myinfluxdb.yml.

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 -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 at oci.influxdata.com. Find the package version you want to upgrade to and copy the version number.

oci.influxdata.com credentials

oci.influxdata.com requires you to log in with credentials provided by InfluxData. If you don’t have these credentials, contact InfluxData Support.

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 at oci.influxdata.com.

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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: