Create a Managed Kafka cluster
Saves a Managed Kafka cluster with status deploying and starts deploying it. An account on a public or disposable email domain, or an API key it made, gets a 403, unless an app setting allows them. A company not yet paying Artie needs a card on file first, or gets a 402. Company admins only.
Authorizations
API key passed as a Bearer token in the Authorization header.
Body
Client IP ranges allowed to reach the cluster. Empty allows any IP; clients still need the password.
3 <= x <= 30m8g.2xlarge, m8g.4xlarge, m8g.xlarge, m8i.2xlarge, m8i.4xlarge, m8i.xlarge, r8g.2xlarge, r8g.large, r8g.xlarge, r8i.2xlarge, r8i.large, r8i.xlarge The cluster's name, as customers see it. 3 to 100 characters. The cluster's ID, which its address and Kubernetes objects use, is generated.
3 - 100Disk per broker in GiB: 20, 50 or 80, or any size from 100 to 1024 (1 TiB). Bigger sizes go through support.
20 <= x <= 1024Whether Artie turns tiered storage on for every topic that hasn't set it either way. The setup form starts it on.
Disk cap per partition: the most broker disk each partition of a tiered topic keeps, in bytes, at least 1073741824 (1 GiB). Null is no cap.
Days on disk: how long tiered topics keep data on broker disks, in ms, from 86400000 (one day) to 1209600000 (14 days). Every topic that doesn't set log.local.retention.ms inherits it. Left out is 3 days.
How Artie grows the brokers' disks before they fill. Left out is on, growing at 65% to 55%, with no limit.
Response
OK
Whether this is a Managed Kafka cluster that Artie runs for the company.
draft, active, deploying, failed, deleted Whether Artie turns tiered storage on for every topic of a Managed Kafka cluster that doesn't choose otherwise.
Whether tiered storage is available on this cluster. Artie turns it on once the cluster's brokers have tiered storage.
When the cluster row last changed. A deploying cluster can be retried 20 minutes after this.
When a deleted Managed Kafka cluster's data is deleted for good. It can be restored until then. Only set while status is deleted.
The step a Managed Kafka cluster's deploy is on. Only set while status is deploying, or failed, where it is the step the deploy stopped at.
applying_custom_resources, issuing_tls_certificate, provisioning_broker_nodes, starting_kafka_brokers, creating_load_balancer Disk cap per partition: the most broker disk each partition of the cluster's tiered topics keeps, in bytes (log.local.retention.bytes). Missing when there is no cap.
Days on disk: how long the cluster's tiered topics keep data on broker disks, in ms (log.local.retention.ms). Missing on clusters made before it, whose brokers use Kafka's default.
A Managed Kafka cluster's configuration. Only set when isManaged, and only by Get a Kafka cluster.
Whether a deleted Managed Kafka cluster is still being taken down. It can't be restored until that finishes. Only set in the clusters list.
Why the last deploy of a Managed Kafka cluster failed. Only set while status is failed.
A Managed Kafka cluster's storage autoscaling. Only set when isManaged.
When the sync last made a Managed Kafka cluster's topics match the tiered storage choice for each. Missing until its first run.

