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
120
0
Share
Easy Microservices in the cloud with Kubernetes and Istio
Sendil Kumar N
November 14, 2019
More Decks by Sendil Kumar N
See All by Sendil Kumar N
[Heapcon-2023] Building High Performance Web Applications
sendilkumarn
0
120
Building Reactive Microservices with Kotlin & running on Kubernetes
sendilkumarn
0
230
Building Reactive Microservices with JHipster & K8s
sendilkumarn
0
40
Designing High Performance React Applications
sendilkumarn
1
210
Batching, Suspense, and Server Components
sendilkumarn
0
83
DevNexus_Building_with__Zero_Trust_Architecture_Copy.pdf
sendilkumarn
0
95
Lessons Learnt with Visual Testing and Snapshots
sendilkumarn
0
150
Easy Microservices with K8s & Istio
sendilkumarn
0
120
KHipster - Kotlin Hipster
sendilkumarn
0
280
Other Decks in Technology
See All in Technology
AIが盛んな時代に 技術記事を書き始めて起きた私の中での小さな変化
peintangos
0
360
GKE Agent SandboxでAIが生成したコードを 安全に実行してみた
lamaglama39
0
210
新卒エンジニア研修、ハンズオンの設計における課題と実践知/ #tachikawaany
nishiuma
2
130
大学職員のための生成AI最前線 :最前線を、AIガバナンスとして読み直すためのTips
gmoriki
2
3.8k
ServiceによるKubernetes通信制御ーClusterIPを例に
miku01
1
150
AIエージェントの支払い基盤 AgentCore Payments概要
kmiya84377
1
140
[Oracle TechNight#99] 生成AI時代のAI/ML入門 ~ AIとオラクルデータベースの関係 (前半)
oracle4engineer
PRO
2
240
カオナビに Suspenseを導入するまで / The Road to Suspense at kaonavi
kaonavi
1
430
Agent Skillsで実現する記憶領域の運用とその後
yamadashy
2
1.4k
SLI/SLO、「完全に理解した」から「チョットデキル」へ
maruloop
1
130
アプリブロック機能のつくりかたと、AIとHTMLの不合理な相性の良さについて
kumamotone
0
120
AI時代に越境し、 組織を変えるQAスキルの正体 / QA Skills for Transforming an Organization
mii3king
5
4.1k
Featured
See All Featured
Sam Torres - BigQuery for SEOs
techseoconnect
PRO
0
260
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
Crafting Experiences
bethany
1
140
GraphQLの誤解/rethinking-graphql
sonatard
75
12k
Learning to Love Humans: Emotional Interface Design
aarron
275
41k
Into the Great Unknown - MozCon
thekraken
41
2.4k
Large-scale JavaScript Application Architecture
addyosmani
515
110k
HDC tutorial
michielstock
2
650
What's in a price? How to price your products and services
michaelherold
247
13k
Making Projects Easy
brettharned
120
6.6k
Automating Front-end Workflow
addyosmani
1370
200k
Documentation Writing (for coders)
carmenintech
77
5.3k
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…