Author(s):	Feilong Wang
Location	Room 8
Date	jan Wed 15	Days Raw Files
Start	10:45	First Raw Start	error-in-template
Duration	0:45:0	Offset	None
End	11:30	Last Raw End
Chapters
Total cuts_time	None min.

https://lca2020.linux.org.au/schedule/presentation/50/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Building_a_zero_downtime_Kubernetes_cluster.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Having recently gone through the experience of building, implementing and running a Kubernetes platform service in its public cloud, Catalyst Cloud has some interesting experiences and war stories to share about the journey. One of the most in-demand for a Kubernetes service's features is monitoring of the cluster’s health and ability of the orchestrator to deal with unhealthy instances and triggering replacements when needed, maximizing the cluster’s efficiency and performance. This presentation and demo are targeted for anybody interested in having closed-loop automation for self-healing and maintenance in a Kuberntes cluster. Attendees will learn how this can be achieved with zero downtime for the user's application. And there are some good tips will be shared about how to runn auto scaling, rolling upgrade and auto healing for Kubernetes cluster. markdown
Comment:	production notes