Multitenancy on EKS

Thursday the 27th of June, 2019
Multi-Tenant*
Platform on EKS
info@container-solutions.com
container-solutions.com
Ian Crosby

container-solutions.com info@container-solutions.com Multi-Tenancy with Kubernetes @IanDCrosby
Agenda
■ Kubernetes Background
■ Introduce Project
■ Architecture
■ Multi Tenancy
■ AWS Integrations
■ Beneﬁts
■ Challenges
■ Life Changing Conclusion

Fast / Customer-Centric
SafeandReliable
LIMITS SPEED,
SAFETY AND
COMPLEXITY
ACHIEVE
QUALITY
THROUGH
SPEED

Microservices

Containers

Virtual Machine vs Container

Orchestration

Container Orchestrators
■ Docker Swarm from Docker
■ Mesos from Apache
■ DC/OS from Mesosphere
■ Nomad from Hashicorp
■ CCP from Cisco
■ OpenShift by Red Hat
■ Fleet by CoreOS (Deprecated)
■ ...

Kubernetes
● Built by Google (Based on Borg)
● Donated to CNCF
● Fully Open Source
● Healthy and Robust Community and Ecosystem

Flavors of Kubernetes
Self Hosted
■ Kubespray
■ Kubeadm
■ K3s
Managed
■ EKS (Amazon)
■ GKE (Google)
■ AKS (Microsoft)
■ IKS (IBM)
PaaS
■ OpenShift
■ Digital Ocean
■ Giant Swarm

Mandate: Migration to EKS
■ Online Platform for Factories
■ Software as a Service
■ Small/medium applications
■ Low traﬃc volume
■ Lots of Clients (and customization)
■ Complete Environment per Customer
■ Entirely AWS Based

vs.
■ Proven Solution
■ Strong Integration
■ Uncertain Future
■ Vendor Speciﬁc
■ Cloud Agnostic
■ More Features
■ Supporting Tooling
■ Cost (?)

Migration Path
■ Containerize Applications
■ Deﬁne Kubernetes Conﬁguration
■ Integrate with AWS Services
■ Incremental Migration
■ Invisible to Dev Team

New Architecture

Multitenancy

... architecture in which a single instance
of software runs on a server and serves
multiple tenants ... designed to provide
every tenant a dedicated share of the
instance - including its data, conﬁguration

Why do we want Multitenancy?
■ Eﬃciency
■ Simplicity
■ Cost

The Risks of Multitenancy
■ Security
■ “Noisy Neighbor”
■ Single Point of Failure

Multi
Instance
Multi
Tenant

Multitenancy on Kubernetes
Leverage native Kubernetes Features
■ Namespaces
■ Network Policies
■ Resource Limits
■ RBAC
■ Ingress

YAML

EKS Cluster

EKS Cluster
Namespace: Client A Namespace: Client B

EKS Cluster
Namespace A Namespace B
Worker Worker

Kubernetes Cluster
Network Policy
Worker Worker

EKS Cluster
Network Policy
Worker
Worker
Worker
Worker
Worker
Worker
Worker Worker

EKS Cluster
Limit RangeLimit Range
Network Policy
Worker
Worker
Worker
Worker
Worker
Worker
Worker Worker

EKS Cluster
Resource Limits
Namespace: Client A
Resource Limits
Namespace: Client B
Network Policy
Client A
Ingress
Controller
Worker
Worker

Kubernetes Cluster
Resource LimitsResource Limits
App 1 App 2
Namespace C Namespace D
App 3 App 4
Namespace E Namespace F
App 5 App 6
Namespace G Namespace H
App 7 App 8

Multitenant-ish

AWS Integrations
ALB Ingress Controller
■ Dynamically spins up Application Load Balancer
■ Built-in Health Checks
■ TLS / Cert Management
■ Subnet and VPN integration

https://aws.amazon.com/blogs/op
ensource/kubernetes-ingress-aw
s-alb-ingress-controller/

AWS Integrations
External DNS
■ Integrates with Route53
■ Dynamically control DNS records

AWS Integrations
CloudWatch
■ Integration with Kubernetes Cluster
■ Application and Platform Metrics
■ Not ideal (yet)

AWS Integrations
Databases (RDS and Elasticache)
■ Don’t manage if you don’t have to
■ Create an abstraction layer
Amazon
Elasticache
Amazon
RDS

Beneﬁts
■ Lower Costs
■ Simpler Setup
■ Easier Client Onboarding
■ Poised for Growth
■ (Less) Vendor Lock-In

Challenges
■ Load Balancing / Ingress
■ Tuning Resource Requests/Limits
■ Application Updates
■ Cluster Size
■ EKS new-ness

Was it all Worth it?

Was it Worth it?
■ Large investment with little *visible* beneﬁt
■ Building for Scale
■ Cost savings + Potential
■ Ready for Further Improvements

Thank You
Questions?
Thanks to unsplash.com for all the pics

Multitenancy on EKS

More Related Content

What's hot

Similar to Multitenancy on EKS

Recently uploaded

Multitenancy on EKS