gcloud managed-kafka clusters create - create a Managed Service for Apache Kafka cluster

gcloud managed-kafka clusters create(CLUSTER :--location=LOCATION)--cpu=CPU--memory=MEMORY--subnets=[SUBNETS,…][--async][--no-auto-rebalance][--encryption-key=ENCRYPTION_KEY][--labels=[KEY=VALUE,…]][--mtls-ca-pools=[MTLS_CA_POOLS,…]][--ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES][GCLOUD_WIDE_FLAG …]

Cluster resource - Identifies the cluster for which the command runs. Thearguments in this group can be used to specify the attributes of this resource.(NOTE) Some attributes are not given arguments in this group but can be set inother ways.

To set theproject attribute:

• provide the argumentcluster on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

CLUSTER

ID of the cluster or fully qualified identifier for the cluster.

To set thecluster attribute:

• provide the argumentcluster on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--location=LOCATION

ID of the location of the Managed Service for Apache Kafka resource. Seehttps://cloud.google.com/managed-service-for-apache-kafka/docs/locationsfor a list of supported locations.To set thelocation attribute:

• provide the argumentcluster on the command line with a fullyspecified name;
• provide the argument--location on the command line.

--cpu=CPU

The number of vCPUs to provision for the cluster. The minimum is 3.

--memory=MEMORY

The memory to provision for the cluster in bytes. The value must be between 1GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi.

--subnets=[SUBNETS,…]

A comma-separated list of VPC subnets from which the cluster is accessible. Bothbroker and bootstrap server IP addresses and DNS entries are automaticallycreated in each subnet. Only one subnet per network is allowed, and the subnetmust be located in the same region as the cluster. The project may differ. Aminimum of 1 subnet is required. A maximum of 10 subnets can be specified. Usecommas to separate multiple subnets. The name of the subnet must be in theformatprojects/PROJECT_ID/regions/REGION/subnetworks/SUBNET.

--async

Return immediately, without waiting for the operation in progress to complete.

--auto-rebalance

Whether the automatic rebalancing is enabled. If automatic rebalancing isenabled, topic partitions are rebalanced among brokers when the number of CPUsin the cluster changes. Automatic rebalancing is enabled by default. Use--no-auto-rebalance to disable this flag. Enabled by default, use--no-auto-rebalance to disable.

--encryption-key=ENCRYPTION_KEY

The relative resource path of the Cloud KMS key to use for encryption in theform:projects/PROJECT_ID/locations/LOCATION/keyRings/KEY_RING/cryptoKeys/KEY.The key must be located in the same region as the cluster. The key cannot bechanged once set.

--labels=[KEY=VALUE,…]

List of label KEY=VALUE pairs to add. Keys must start with a lowercase characterand contain only hyphens (-), underscores (_),lowercase characters, and numbers. Values must contain only hyphens(-), underscores (_), lowercase characters, andnumbers.

--mtls-ca-pools=[MTLS_CA_POOLS,…]

A comma-separated list of CA pools from the Google Cloud Certificate AuthorityService. The root certificates of these CA pools will be installed in thetruststore of each broker in the cluster for use with mTLS. A maximum of 10 CApools can be specified. CA pools can be in a different project and region thanthe cluster. This command overwrites the entire set of pools currentlyconfigured on the cluster. If you want to add a new pool to an existingconfiguration, you must provide the full list of both the old and new CA poolsin the command. Each CA pool must be in the formatprojects/PROJECT_ID/locations/LOCATION/caPools/CA_POOL.Clear the CA pools using the--clear-mtls-ca-pools flag.

--ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES

The rules for mapping mTLS certificate Distinguished Names (DNs) to shortenedprincipal names for Kafka ACLs. This flag corresponds exactly to thessl.principal.mapping.rules broker config and matches the formatand syntax defined in the Apache Kafka documentation. Setting or modifying thisfield will trigger a rolling restart of the Kafka brokers to apply the change.An empty string means that the default Kafka behavior is used. Example:"RULE:^CN=(.?),OU=ServiceUsers.$/$1@example.com/,DEFAULT"

Run$gcloud help for details.