- Hosted by @jbeda
- Hosted by @krisnova
- Recording date: 2019-03-22
<a href="https://www.youtube.com/watch?v=
" target="_blank">
- 00:00:00 - Welcome to TGIK!
- 00:00:00 - Week in Review
- New scope doc in github.com/kubernetes/kubernetes
- The documentation for HTTP readiness and liveness probes has always said that any HTTP response with a code between 200 and 400 would be considered a success, but until now 301 and 302 redirects have been expanded by the kubelet and queried again. As a compromise between matching the spec and not overly breaking backwards compatibility, redirects to the same hostname as used originally will still be followed, but a redirect to a new hostname will be considered a success and not followed. This may result in a loss of accuracy in some very rare cases such as clustered applications redirecting to each other. But on the plus side it improves the security of Kubernetes and closes a potential traffic amplification vector.
Kubeweekly https://t.co/JtzIHddg3D
- Shout out to Tim St. ClairThe what and why of cluster-api
- Shout out to Marko Mudrinic for "running kubernetes in ci (with kind!)"
- Shout out to Paris Pittman for a retro and look forward on contributor summit
"Overjoyed" in Icelandic
Built on envoy. Great quote below.
so the tldr on gloo: you know how istio, ambassador, contour, etc are all just ways of configuring envoy on kubernetes? Gloo decomposed that process down into more fundamental types https://gloo.solo.io/dev/ making it really a way to build envoy configuration services.