KafkaTopic CRs have a relatively simple base set of settings: name, partitions, replication.factor. But there are a significant number of configurations that can be applied. Discovering the correct name, what they mean, the allowed (or recommended) values is very difficult. Also, key settings like retention are difficult to visualise and get correct: "how many milliseconds are there in 2 days", "if I set retention bytes to this value, how much disk space could it take up in the worst case?".
We should explore what the UX of a KafkaTopic design UI could look like and discuss the features we think would be useful to users.
KafkaTopicCRs have a relatively simple base set of settings: name, partitions, replication.factor. But there are a significant number of configurations that can be applied. Discovering the correct name, what they mean, the allowed (or recommended) values is very difficult. Also, key settings like retention are difficult to visualise and get correct: "how many milliseconds are there in 2 days", "if I set retention bytes to this value, how much disk space could it take up in the worst case?".We should explore what the UX of a
KafkaTopicdesign UI could look like and discuss the features we think would be useful to users.