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!


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.

Read more

New in InfluxDB 3.4

Key enhancements in InfluxDB 3.4 and the InfluxDB 3 Explorer 1.2.

See the Blog Post

InfluxDB 3.4 is now available for both Core and Enterprise, which introduces offline token generation for use in automated deployments and configurable license type selection that lets you bypass the interactive license prompt. InfluxDB 3 Explorer 1.2 is also available, which includes InfluxDB cache management and other new features.

For more information, check out: