[Seminar co-hosted by Yahoo!] MixLeap Study #68 - Learning about Kubernetes operations from case studies

Yahoo! Japan Corporation 's event "Mix Leap Study" and Beyond are collaboratingKubernetes to host an online study session on the theme of
About the event
"Mix Leap Study" is a study group held at the Yahoo! Osaka office, with the aim of helping creators (engineers and designers) in the Kansai region grow by exposing them to a variety of Yahoo!'s unique technologies and cutting-edge technologies in the industry
We aim to become a crossroads for people and information by bringing together students interested in IT and working adults working in IT companies to communicate with each other
This time's theme
This time, the study group will focus on the theme of "Kubernetes operation."
Three engineers who are in charge of Kubernetes operations in their daily work will talk about their company's use cases, operational challenges, and future developments
In the second half of the event, there will also be a panel discussion on the topic of "Challenges in Kubernetes operation" submitted by participants
- Considering using/introducing Kubernetes
- I'm involved with Kubernetes and would like to know about other companies' examples
This event is especially recommended for engineers who:
Timetable
Presentation time: 15 minutes / Q&A: 5 minutes
| time | Content | speaker |
|---|---|---|
| 18:55 - 19:00 | Live Streaming Information | |
| 19:00 - 19:05 | Opening remarks | Michitaro Nakajima (Yahoo Japan Corporation) |
| 19:05 - 19:25 | "Pod and Worker Node Behavior Under High Load in GKE" | Yuki Teraoka (Beyond Inc.) |
| 19:25 - 19:45 | "Learn Kubernetes configuration by comparing manifests" | Keisuke Yabuta (Yahoo Japan Corporation) |
| 19:45 - 20:05 | "Near miss cases in Kubernetes operation" | Takuya Yamada (Yahoo Japan Corporation) |
| 20:05 - 20:25 | Panel Talk | |
| 20:25 - 20:30 | Closing |
*Depending on the progress of the event, the end time may vary slightly
Speaker Information
Speaker: Yuki Teraoka
Joined Beyond in 2016, I am currently in my sixth year
as an infrastructure engineer and MSP. I handle troubleshooting during incidents while also designing and building infrastructure using public clouds such as AWS.
Recently, I have been frequently working with container infrastructure such as Docker and Kubernetes, and with HashiCorp tools such as Terraform and Packer as part of operational automation. I also take on the role of an evangelist, speaking at external study groups and seminars.
| title | Behavior of Pods and Worker Nodes under high load in GKE |
|---|---|
| overview | When running any service or system using Kubernetes, you will most likely utilize managed services provided by AWS, GCP, etc. This time, using GKE as an example, we will organize the behavior of Pods and Worker Nodes when the Cluster becomes heavily loaded during operation, and discuss how to deal with and respond to such loads. |
Speaker: Keisuke Yabuta
Joined Yahoo! in 2017.
Engaged in the development and operation of the platform supporting Yahoo!'s services.
Primarily focused on backend development, including system and network architecture considerations, and recently also involved in frontend development.
| title | Learn Kubernetes configuration by comparing manifests |
|---|---|
| overview | I will introduce two examples of products that use Kubernetes, and discuss why things are the way they are based on the differences in their manifests, what settings you should make, and what settings you should avoid |
Speaker: Takuya Yamada
After joining Yahoo! in 2017, I was responsible for the development and operation of the image distribution platform.
Currently, I am in charge of developing the nearest neighbor search engine platform.
| title | Near miss cases in Kubernetes operation |
|---|---|
| overview | I'd like to share some particularly memorable near-misses from my approximately three and a half years of Kubernetes operation and development. I'll reflect on the causes and solutions at the time, hoping to share some know-how to prevent similar problems in the future. |
