First, see the updated docs to if you’re still wondering what Kubernetes is.
Then, refer to the summary blog posts from people that were actually at KubeCon:
& Summaries after the Conference finished:
What I pieced together from the Twitter Stream:
Kubernetes 1.2 available by end of March 2016 - UPDATE: Released on March17
Deployments manage ReplicaSets based on a template. Updating the template will make deployments act based on the difference of Desired vs Actual state, i.e. version updates will result in a rolling update (w/ zero downtime) - Released on Deployment Docs
Config Maps - ConfigMap docs - late-binding, live-updated and atomic. Take the pod configuration out of the pod and let the kubelet provision it (either as env vars or config files mounted into the pod). Secrets were used to late bind config, Config Maps are designed as a better solution for this requirement. (see also: Kubernetes/Issues/12732 - Keys/Certs generation for services)
DaemonSet (i.e. cluster-wide node agents for logging / networking / storage / … )
Cloud Native Computing Foundation (CNCF): Linux Foundation Collaborative project aiming to advance a common set of open source tech to accelerate adoption of microservices, containers and cloud native applications. CNCF Accepts k8s as First Hosted Project - 1 goal is to establish a 1000-node cluster for the CNCF community to run and validate Cloud Native applications and infrastructure at scale.
Used by a lot of KubeCon demos: Weave Scope provides a visual map of your Docker containers, so you can intuitively understand, monitor, and control your applications. Scope comes with built-in Kubernetes support. Use Scope to visualize Calico
Cloud-Native SDN for Kubernetes - slides - Romana: CNI plugin for k8s. With Romana you won’t have the overhead of a virtual network overlay so your Nodes will communicate more directly without tunnels or encapsulation - Video from demo at Meetup. See also Running k8s with Romana & Slides from Meetup.
SDN - See also: Scalable networking with Calico
SDN - See also: Open Contrail on pannel discussion - ref: k8s & OpenSTack
persistent volumes providing cluster-wide non-ephemeral storage. A couple of different cluster storage providers are available for persistent volumes in k8s: More classic ones like NFS and SCSI; cloud native ones like GlusterFS and Ceph; cloud provider specific ones for GCE and AWS and storage abstraction layers like Flocker.
--maximum-dead-containers=100 --maximum-dead-containers-per-container=2 --minimum-container-ttl-duration=1m0s
Best practice for CI/CD on k8s seems to be: separate different applications and stages by using k8s namespaces and use ChatOps tools like Hubot (https://hubot.github.com) to provide fast feedback to the devs & ops.
Hypernetes - https://hyper.sh/ (Similar to ClearOS from intel?)
1.2 milestones & Google Cloud Platform Podcast with Kelsey Hightower (starts at 06:20)
Apprenda Sales pitch? Hybrid Apps: Orchestrating Cloud Native and Traditional Application Architectures by @sschuller
RedHat OpenShift: The Red Hat Ecosystem for Microservice and Container Development - tag: Kubernetes
Templatized Application configuration - Resources
Transforming the Government - notice: UKHomeOffice/vault-sidekick
Last updated: Wednesday, March 17