Containers: Not Just for the Cloud?
summary
Practical checklist for on‑prem containers: require Red Hat 7 and preinstall Docker and Kubernetes packages, then transfer images with docker save/load (FedEx USB is fine) and initialize the cluster offline with kubeadm/install scripts; keep databases and heavy I/O stores outside the cluster for backups and DBA buy‑in; ship versioned image bundles for upgrades; monitor base images and vulnerabilities (BlackDuck or similar) and use the Kubernetes dashboard plus an ELK stack for logs and restore-tested backups.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:27Show of hands... • Who has just one deployment of their containerized application and sells it as Saas? . ... and who does on-premises? • How do you orchestrate your containers?
- 13:46Inside the cluster or out? • Corporate DBA often tightly regulates databases and won't want them buried inside a black box
- 16:52Security updates • The usual containers answer: "just" rebuild and redeploy them regularly • Our approach: centralized audit of base images + mailing list monitoring for security alerts
- 21:52Backup and recovery • If you're just running it yourself in AWS image snapshots + RDS automatic backups • Need a documented tested!! process for the dient to run on-site
- 26:56What about Windows? • Microsoft, Docker and Ks developers are working very hard to solve that for us • For now we have a proposed compromise where a Linux VM runs stateless K8s services and the data stores/IO intensive bits run directly on Windows
related talks
32mWhy you´re not ready for Containers in Production!
05mAdopting a dockerized workflow
26mContainerization crossroads: Experiences-Experiments-Expectations
31mDockerized app in production? YES WE CAN!!
47mContinuous Delivery with Containers: The Good, Bad, & Ugly
52mNot your Grandmother's On-Prem
44mTop 5 container and Kubernetes best practices
46mFrom Docker To Kubernetes: A Developer's Guide To Containers