Hey everyone, This is a new SIP, not a duplicate of SIP-17 (Authoscaling on Kubernetes), and completely unrelated.
Basically there is a lot of very messy logic we do in the Solr Operator to bootstrap security and manage various things. This logic must exist because Solr has no idea that Kubernetes exists. If we can use Kubernetes APIs to pull in information, instead of relying on the Solr Operator to inject that information in hacky-ways, the user experience on Kubernetes is going to get many times better for users wanting to secure their SolrClouds. This will also help us use authorization by default (which we always preach) via the Solr Operator. This SIP is not very filled out because I'm still thinking on various aspects. But in general, we can attack the different plugins one-by-one and the SIP can evolve throughout the process. This SIP is very easy to break up, which is nice. Please let me know if I can explain more, or how I can make the SIP page better. - Houston
