Still a fair amount of the glue and interspersed code that wires it together sits outside, plus the user management code (user, group, identity integration to a

Still a fair amount of the glue and interspersed code that wires it together sits outside, plus the user management code (user, group, identity integration to all the various providers). Also all the out of the box default security. Part of the benefit of being slightly apart from Kube initially (which we did because we had way too many things we wanted to bring together to put into Kube at the time) is that we could be opinionated and say things like: * every component will use client cert + TLS + specific authorization roles to interconnect * no ability to configure the cluster without those on * default to secure by default, be opinionated about authz/n * lock down everything that could be abused (like letting end users change ingress IPs on services, or direct volume mounting) * make namespaces the unit of tenancy and restrict regular users from modifying most things in namespaces that impact policy The raw pieces are in Kube now, but effecting the same opinionated defaults while still preserving the flexibility many in the community want (like direct Keystone integration, or no restrictions on pods by default) will take some time. Our goal is to get there in a way that also makes Kube more extensible and flexible - I don't believe everyone needs everything we believe in, but by doing it in pieces we do get to ensure it's possible for someone else to do it.