Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Easy Microservices in the cloud with Kubernetes...
Search
Sendil Kumar N
November 14, 2019
Technology
0
96
Easy Microservices in the cloud with Kubernetes and Istio
Sendil Kumar N
November 14, 2019
Tweet
Share
More Decks by Sendil Kumar N
See All by Sendil Kumar N
[Heapcon-2023] Building High Performance Web Applications
sendilkumarn
0
82
Building Reactive Microservices with Kotlin & running on Kubernetes
sendilkumarn
0
180
Building Reactive Microservices with JHipster & K8s
sendilkumarn
0
21
Designing High Performance React Applications
sendilkumarn
1
150
Batching, Suspense, and Server Components
sendilkumarn
0
40
DevNexus_Building_with__Zero_Trust_Architecture_Copy.pdf
sendilkumarn
0
58
Lessons Learnt with Visual Testing and Snapshots
sendilkumarn
0
110
Easy Microservices with K8s & Istio
sendilkumarn
0
93
KHipster - Kotlin Hipster
sendilkumarn
0
240
Other Decks in Technology
See All in Technology
Swiftは最高だよの話
yuukiw00w
2
290
Zero Data Loss Autonomous Recovery Service サービス概要
oracle4engineer
PRO
2
7.2k
libsyncrpcってなに?
uhyo
0
150
他チームへ越境したら、生データ提供ソリューションのクエリ費用95%削減へ繋がった話 / Cross-Team Impact: 95% Off Raw Data Query Costs
yamamotoyuta
0
240
FastMCPでSQLをチェックしてくれるMCPサーバーを自作してCursorから動かしてみた
nayuts
1
220
Scale Security Programs with Scorecarding
ramimac
0
440
いまさら聞けない Git 超入門 〜Gitって結局なに?から始める第一歩〜
devops_vtj
0
170
AIエージェントデザインパターンの選び方
almondo_event
0
150
Java で学ぶ 代数的データ型
ysknsid25
1
520
エンジニアが組織に馴染むために勉強会を主催してチームの壁を越える
ohmori_yusuke
2
120
大事なのは、AIの精度だけじゃない!〜1円のズレも許されない経理領域とAI〜
jun_nemoto
11
5.2k
OSMnx Galleryの紹介
mopinfish
0
150
Featured
See All Featured
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
123
52k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
A Modern Web Designer's Workflow
chriscoyier
693
190k
Mobile First: as difficult as doing things right
swwweet
223
9.6k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
34
2.3k
What’s in a name? Adding method to the madness
productmarketing
PRO
22
3.5k
Code Review Best Practice
trishagee
68
18k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
42
2.3k
Fireside Chat
paigeccino
37
3.5k
Why You Should Never Use an ORM
jnunemaker
PRO
56
9.4k
How to train your dragon (web standard)
notwaldorf
92
6k
We Have a Design System, Now What?
morganepeng
52
7.6k
Transcript
Sveiki Lithuania
Questions @ sli.do
Easy microservices in the cloud with Kubernetes & Istio
Sendil Kumar @sendilkumarn
None
None
Senior Software Engineer @uber
Passionate about Open Source Senior Software Engineer @uber
Passionate about Open Source Senior Software Engineer @uber Team member
@JHipster
Passionate about Open Source Senior Software Engineer @uber Team member
@JHipster Crafting @KHipster
Agenda K8s Istio JHipster Microservices JHipster Microservices K8s & Istio
Docker
Docker Self Contained images
Docker Self Contained images Portability
Docker Managing the infrastructure
Docker Managing the infrastructure Deciding when and how to run
the applications
Kubernetes
Kubernetes De-coupled infrastructure completely
K8s is an open-source system
K8s is an open-source system that automates deployment containerised applications
K8s is an open-source system that automates deployment scales (up/down/in/out)
Containerised applications
K8s is an open-source system that automates deployment scales (up/down/in/out)
manages Containerised applications
K8s makes it easy and simple
But K8s itself is not simple
How Kubernetes works?
Cluster mode
Kubernetes Master Nodes Nodes Nodes
kubectl apply -f some.yml Api Server etcd Scheduler Controller create
yaml file connects via CLI adds to the queue stores sends to the controller Kubernetes Land
Api Server etcd Scheduler Controller Kubernetes Land Control Plane
Worker Node signals to start the deployment Kubelet Kubelet Kubelet
Worker Node Kubelet Kubelet Kubelet Worker Node Kubelet Kubelet Kubelet Scheduler
handles networking Worker Node Kubelet Kube proxy Kubelet Kube proxy
Kubelet Kube proxy Kubelet Kube proxy
K8s states the (desired) running state of application
Microservices
more freedom to react Microservices
respond faster Microservices
Technology Heterogeneity
Fault isolation
Granular Scaling
❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌ ❌
Don’t violate DRY inside microservice.
Microservices with JHipster
API Gateway BFF Pattern
How does JHipster app looks like?
Java / Kotlin backend Zuul UAA
Java / Kotlin backend Zuul UAA Microservices Gateway
Service Registry
JHipster Registry Consul
JHipster Registry Consul Eureka + Spring Cloud Config Admin Server
Easier in multi-node cluster Availability over consistency Consistency over Availability - All nodes provide correct detail every time
Consoles
Elasticsearch Logstash Kibana JHipster Console
Consul / JHipster Registry Console Microservices Gateway Microservices
We will generate…
Store Gateway Notification Invoice Product
JHipster demo time
None
Harder to control
Harder to Manage
Harder to Secure
Service A Service B Service C
Service A Service B Service C Logging Monitoring Networking
Service A Service B Service C Common Services…
Istio
Service mesh
network of inter connected microservices
Without any changes in your services
Without any changes in your services Control Connect Secure Observe
But how Istio does it?
App PROXY Envoy proxy
Envoy proxy Lightweight c++ protocol Platform-agnostic Network abstraction
App PROXY Mixer Policy control Telemetry collection
App PROXY Mixer Control Plane
Control Plane App PROXY Mixer Pilot Galley Citadel Service discovery
Validate, process & distribute Authentication
Control Plane App PROXY Mixer Pilot Galley Citadel Service discovery
Validate, process & distribute Authentication Data plane
Control Plane App PROXY Mixer Pilot Galley Citadel Control Connect
Secure Observe
JHipster kubernetes
• Kubernetes + Istio configuration • Running in GCloud
The best practices
Single Responsibility Principle Smaller YAML files Split the files
Smaller image sizes Alpine images for the win Faster to
boot
Healthy - Zombie
Single process in a container… Docker don’t know which process
crashed
Services - RED pattern Requests - Errors - Duration pattern
RED
Resources - USE pattern Utilization - Saturation - Errors pattern
Think about Requests / Limits
Clean up unused resources
Monitor and tune
Questions…
Thanks…