may need VMs for isolation Prepare to fight with Docker about networking Candidates: • VMs for isolation • Pay for SDN layers • FFS! Use Kubernetes for the right things
it depends on are also releasing Expect clusters to have different versions Candidates: • Plan for Day 2 upgrades • Consider immutable deployments • Reduce blast radius with smaller clusters
apps mean dynamic registrations Oh… are you thinking about IPv6 too? Candidates: • OpenDNS integrated into Kubernetes • Need to integrate & delegate domains
be required Firmware will actually matter Stuffing in VMs may not be enough Candidates: • Automate, automate, automate • Immutable imaging helps • Consult your distro requirements Operating System & Host Provisioning
distro / appliance it needs to fit into your infrastructure. Expect to pay for distro AND consulting Candidates: • Gingerbread man… • Look at your broader needs • Trunk distros are OK, but...
not an island • Integration is key - make sure to plan for it • Fix root cause issues (bare metal / provisioning) • Start with Day 2 / Lifecycle questions • Worth Repeating: FFS! Use Kubernetes for the right things If you want to see how RackN is thinking about this, please check out our Kubernetes + Rebar Integration (KRIB).
clusters are more common; however this may reflect small is the starting point. For on-prem, small clusters on VMs makes a lot of sense; however, I expect a shift to large clusters to replace cloud for the data center underlay.