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
92
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
72
Building Reactive Microservices with Kotlin & running on Kubernetes
sendilkumarn
0
160
Building Reactive Microservices with JHipster & K8s
sendilkumarn
0
18
Designing High Performance React Applications
sendilkumarn
1
140
Batching, Suspense, and Server Components
sendilkumarn
0
33
DevNexus_Building_with__Zero_Trust_Architecture_Copy.pdf
sendilkumarn
0
55
Lessons Learnt with Visual Testing and Snapshots
sendilkumarn
0
100
Easy Microservices with K8s & Istio
sendilkumarn
0
85
KHipster - Kotlin Hipster
sendilkumarn
0
220
Other Decks in Technology
See All in Technology
第3回Snowflake女子会_LT登壇資料(合成データ)_Taro_CCCMK
tarotaro0129
0
200
大幅アップデートされたRagas v0.2をキャッチアップ
os1ma
2
540
NW-JAWS #14 re:Invent 2024(予選落ち含)で 発表された推しアップデートについて
nagisa53
0
270
Wantedly での Datadog 活用事例
bgpat
1
520
UI State設計とテスト方針
rmakiyama
2
640
ずっと昔に Star をつけたはずの思い出せない GitHub リポジトリを見つけたい!
rokuosan
0
150
フロントエンド設計にモブ設計を導入してみた / 20241212_cloudsign_TechFrontMeetup
bengo4com
0
1.9k
開発生産性向上! 育成を「改善」と捉えるエンジニア育成戦略
shoota
2
400
Turing × atmaCup #18 - 1st Place Solution
hakubishin3
0
490
複雑性の高いオブジェクト編集に向き合う: プラガブルなReactフォーム設計
righttouch
PRO
0
120
[Ruby] Develop a Morse Code Learning Gem & Beep from Strings
oguressive
1
170
LINEヤフーのフロントエンド組織・体制の紹介【24年12月】
lycorp_recruit_jp
0
530
Featured
See All Featured
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
47
5.1k
Making the Leap to Tech Lead
cromwellryan
133
9k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
The Invisible Side of Design
smashingmag
298
50k
Git: the NoSQL Database
bkeepers
PRO
427
64k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
28
9.1k
Building Your Own Lightsaber
phodgson
103
6.1k
A Modern Web Designer's Workflow
chriscoyier
693
190k
A Tale of Four Properties
chriscoyier
157
23k
Faster Mobile Websites
deanohume
305
30k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
127
18k
KATA
mclloyd
29
14k
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…