Documentation

Remove a user from your InfluxDB cluster

Remove a user with administrative access from your InfluxDB cluster:

  1. Remove or deactivate the user in your identity provider.

    Refer to your identity provider’s documentation for information about removing users:

  2. Remove the user from your InfluxDB AppInstance resource. You can edit your AppInstance resource directly in your myinfluxdb.yml, or, if you’re using the InfluxDB Clustered Helm chart, you can remove users from your values.yaml to modify your AppInstance resource.

    If editing your AppInstance resource directly, remove the user from the list of users in the spec.package.spec.admin.users field in your myinfluxdb.yml configuration file–for example:

    apiVersion: kubecfg.dev/v1alpha1
    kind: AppInstance
    # ...
    spec:
      package:
        spec:
          admin:
            # ...
            users:
            - id: XXooXoXXooXXXoo1
              firstName: Marty
              lastName: McFly
              email: mcfly@influxdata.com
    -       - id: XXooXoXXooXXXoo2
    -         firstName: John
    -         lastName: Doe
    -         email: j.doe@influxdata.com
    

    If using the InfluxDB Clustered Helm chart, remove the user from the list of users in the admin.users field in your in your values.yaml–for example:

    admin:
      # ...
      users:
        - id: XXooXoXXooXXXoo1
          firstName: Marty
          lastName: McFly
          email: mcfly@influxdata.com
    -   - id: XXooXoXXooXXXoo2
    -     firstName: John
    -     lastName: Doe
    -     email: j.doe@influxdata.com
    
  3. Apply the change to your InfluxDB cluster.

    • If updating the AppInstance resource directly, use kubectl to apply the change.
    • If using the InfluxDB Clustered Helm chart, use helm to apply the change.
kubectl apply \
  --filename myinfluxdb.yml \
  --namespace influxdb
helm upgrade \
  influxdb \
  influxdata/influxdb3-clustered \
  -f ./values.yaml \
  --namespace influxdb

After you complete step 1 above, the removed user no longer has administrative access to your InfluxDB cluster. However, you should still remove them from your AppInstance resource.


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