Skip to main content
Version: 23.1

rpk acl list

List ACLs.

See the rpk acl help text for a full write up on ACLs. List flags work in a similar multiplying effect as creating ACLs, but list is more advanced: listing works on a filter basis. Any unspecified flag defaults to matching everything (all operations, or all allowed principals, etc).

As mentioned, not specifying flags matches everything. If no resources are specified, all resources are matched. If no operations are specified, all operations are matched. You can also opt in to matching everything with "any": --operation any matches any operation.

The --resource-pattern-type, defaulting to "any", configures how to filter resource names:

  • "any" returns exact name matches of either prefixed or literal pattern type
  • "match" returns wildcard matches, prefix patterns that match your input, and literal matches
  • "prefix" returns prefix patterns that match your input (prefix "fo" matches "foo")
  • "literal" returns exact name matches

Usage

rpk acl list [flags]

Aliases

list, ls, describe

Flags

ValueTypeDescription
--allow-hoststringsAllowed host ACLs to match (repeatable).
--allow-principalstringsAllowed principal ACLs to match (repeatable).
--cluster-Whether to match ACLs to the cluster.
--deny-hoststringsDenied host ACLs to match (repeatable).
--deny-principalstringsDenied principal ACLs to match (repeatable).
--groupstringsGroup to match ACLs for (repeatable).
-h, --help-Help for list.
--operationstringsOperation to match (repeatable).
-f, --print-filters-Print the filters that were requested (failed filters are always printed).
--resource-pattern-typestringPattern to use when matching resource names (any, match, literal, or prefixed) (default "any").
--topicstringsTopic to match ACLs for (repeatable).
--transactional-idstringsTransactional IDs to match ACLs for (repeatable).
--admin-api-tls-certstringThe certificate to be used for TLS authentication with the Admin API.
--admin-api-tls-enabled-Enable TLS for the Admin API (not necessary if specifying custom certs).
--admin-api-tls-keystringThe certificate key to be used for TLS authentication with the Admin API.
--admin-api-tls-truststorestringThe truststore to be used for TLS communication with the Admin API.
--brokersstringsComma-separated list of broker ip:port pairs (e.g. --brokers '192.168.78.34:9092,192.168.78.35:9092,192.179.23.54:9092'). Alternatively, you may set the REDPANDA_BROKERS environment variable with the comma-separated list of broker addresses.
--configstringRedpanda config file, if not set the file will be searched for in the default locations.
--passwordstringSASL password to be used for authentication.
--sasl-mechanismstringThe authentication mechanism to use. Supported values: SCRAM-SHA-256, SCRAM-SHA-512.
--tls-certstringThe certificate to be used for TLS authentication with the broker.
--tls-enabled-Enable TLS for the Kafka API (not necessary if specifying custom certs).
--tls-keystringThe certificate key to be used for TLS authentication with the broker.
--tls-truststorestringThe truststore to be used for TLS communication with the broker.
--userstringSASL user to be used for authentication.
-v, --verbose-Enable verbose logging (default: false).

What do you like about this doc?




Optional: Share your email address if we can contact you about your feedback.

Let us know what we do well: