to get the best utilization of our infrastructure” “Keeping our infrastructure perfectly homogenous is giving me nightmares” “It ran fine on MY machine” “My developers aren’t as productive as they should be. Deployments are slowing us down”
containers on VMs, I don’t want to manage anything” “How do I get my containers to talk to one another?” “Where should I run my containers? “How do we ensure our containers are running smoothly?”
physical or virtual machine running Kubernetes, onto which pods can be scheduled. Pod : A pod is a co-located group of containers and volumes. Label : A label is a key/value pair that is attached to a resource to convey a user-defined identifying attribute. Selector : A selector is an expression that matches labels in order to identify related resources. Replication Controller : A replication controller ensures that a specified number of pod replicas are running at any one time. Handles re-creation of a pod when the machine it is on reboots or otherwise fails. Concepts Service : A service defines a set of pods and a means by which to access them, using IP addresses and DNS. Volume : A volume is a directory accessible to a Container as part of its filesystem. Builds upon Docker Volumes, adding provisioning of the volume directory and/or device. Secret : A secret stores sensitive data, such as authentication tokens, which can be made available to containers upon request. Name : A user- or client-provided name for a resource. Namespace : A namespace is like a prefix to the name of a resource.
nodes run a copy of a pod Deployments : declarative update for Pods and Replication Controllers Ingress Resources : rules for allowing inbound connections to reach cluster services Horizontal Pod Autoscaling : allows the number of pods in a replication controller or deployment to scale automatically based on observed CPU utilization Jobs : creates one or more pods and ensures that a specified number of them successfully terminate. As pods successfully complete, the job tracks the successful completions. New in 1.1
managed resources Run clusters on a bundle of Google Compute Engine resources: Instances, Disks, Networking, Load Balancer Built-in support for centralized logging and container health checking Private container registry at gcr.io
cloud.google.com/container-engine Solutions Continuous Deployment on Kubernetes Automated Image Builds with Jenkins, Packer, and Kubernetes Distributed Load Testing using Kubernetes Real-time data analysis with Kubernetes, Google Cloud Pub/Sub, and BigQuery Real-time data analysis with Kubernetes, Redis, and BigQuery