Listing Organizations

Cluster administrators can list every organization in the cluster with the Fuzzball CLI subcommand organization list. Use it to find the organization IDs needed by other administrative commands. There is no web UI equivalent.

This command is restricted to cluster administrators. Organization owners who want to see their own organization should use fuzzball organization get instead.

• Cluster administrator permissions
• Fuzzball CLI with a context configured and logged in as a cluster administrator

$ fuzzball organization list
ID                                   | NAME              | PRIORITY
c9261ae5-1a31-4e88-bc74-5520ca661ec4 | Test-Organization | 0
f35fcdd4-e702-450e-a060-7d1d51519d07 | FuzzballTesting   | -5

The PRIORITY column shows each organization’s scheduling priority as a signed integer, 0 by default. The scheduler combines it with the account, user, and workflow priorities and with job age to compute an effective priority; a higher effective priority is scheduled sooner. In the example above, Test-Organization (0) is scheduled ahead of FuzzballTesting (-5). The expression that combines these inputs is the scheduler.priority setting documented in the Configuration Reference.

For the complete record of every organization, including create and update timestamps, use YAML or JSON output:

$ fuzzball organization list --output yaml
$ fuzzball organization list --output json

--page-size controls how many records the server returns per request, not how many are displayed – the CLI walks every page and prints the full set in one table. --max-pages is different: it stops the walk early, so the table can be incomplete. The CLI prints a warning to stderr when it truncates a result this way.

Other administrative commands take an organization ID from this listing. For example, to set an organization’s scheduling priority:

$ fuzzball organization update c9261ae5-1a31-4e88-bc74-5520ca661ec4 --priority -5

The fuzzball-admin CLI in the fuzzball-admin-0 pod can also list organizations. It bypasses the Fuzzball API and requires kubectl access to the cluster, so prefer fuzzball organization list above. It emits JSON rather than a table, and supports --page-size, --filter, and --order-by in long form only:

$ kubectl exec -n fuzzball fuzzball-admin-0 -- /app/fuzzball-admin organization list
{
  "organizations": [
    {
      "id": "c9261ae5-1a31-4e88-bc74-5520ca661ec4",
      "name": "Test-Organization",
      "create_time": {
        "seconds": 1720561766,
        "nanos": 239478000
      },
      "update_time": {
        "seconds": 1720561766,
        "nanos": 239478000
      }
    }
  ]
}