Heya, Thanks for the KIP!
I am not convinced that making --bootstrap-server/--bootstrap-controller optional in kafka-features is needed. I understand that there is a difference with how kafka-storage works, but the two CLIs are meant to be used in different situations - kafka-storage is meant to be used during a setup leading to a working cluster while kafka-features allows dynamic interactions with an already working cluster. I further understand that you might want to use this tool in an automation, but I don't quite understand to what purpose - this isn't dynamic information i.e. it will only change during a new release and you can just point to that release's kafka-storage tool to get the same information, no? I am more intrigued by the second part of the KIP. As far as I am understanding it, you would like to see what features are unstable, or at least which version numbers of a feature are unstable so that you don't enable them accidentally? Best, Christo
