Keynote: KubeCon Opening Keynote - Kelsey Hightower, Google
Why Hacker News recommends it
HN mentions it mainly as an example of Hightower's live-demo keynotes and a demo of pull-request-driven promotion and deployment.
What it is
Kelsey Hightower's opening keynote at KubeCon, delivered as a live-demo style talk about Kubernetes and cloud-native tooling.
Recommended by 0 HN commenters across 0 different months, 2018 to 2018.
What Hacker News said
Cites merb · 2018-03 · on “Show HN: Gitkube – Deploy to Kubernetes Using Git Push”
well the problem with openshift on redhat/centos/atomic/whatever is that you still need to regulary update your cluster os's. however when you setup a bootkubed/self-hosted kubeadm cluster you can basically run on coreos and only need to update your self-hosted control plane and kubelet/(etcd, if not self hosted, too) this makes it way, way easier to have an up-to-date os + kube than any other solution (kubelet and etcd can be updated via etcd-wrapper and kubelet-wrapper, so this is even more insane). BUT i think that red hat pushes for an easier upgrade path anyway, that's why they basically bought coreos. for CoreUpdate + Tectonic + MatchBox, so I think that in the end Redhat will have a s
Cites kronin · 2018-04 · on “Jenkins X: a CI/CD solution for cloud applications on Kubernetes”
Please don't. I am using gitlab, though we quickly grew beyond auto devops. Your definition of auto devops is different than gitops. Gitops is the practice of using commits and pull requests to execute change and do releases. Weave uses it to mean git as the source of truth. [LINK] Kelsey Hightower talked about it and and has demoed the workflow of using pull requests to initiate promotion and deployments. Gitlab's auto devops does not seem to tackle promotion via environment repos, so in my understanding does not fit gitops and would be confusing to call it such. Edit: Kelsey Hightower's kubeconf talk - [this video] And a better writeup on weave's site - [LINK]
Cites aberoham · 2018-10 · on “Teleport v3.0 introduces Kubernetes support”
Kubernetes projects leads would argue that any time a user has to SSH into one of their K8s workers, they should file a bug against Kubernetes. At KubeCon CPH, when I asked Tim Hockin about the long-awaited debug containers feature, aka 'kubectl debug', he said that "I really do feel that every time someone has to SSH into a node a ferry loses its wings." :) Dropping out of or below the cluster layer inherently means there is something in K8s that is missing. But no matter what is added to its APIs, Kubernetes will experience a long tail of weird corner cases that just can’t be covered. Reportedly the same is true with Borg jobs internally within Google. Teleport's K8s protocol implementatio