Modernizing on EKS (Keynote)- AWS Container Day 2019 Barcelona

© 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Amazon Confidential and Trademark
1
How are customers modernizing on EKS?

2
Speaker Intro – wisebob@amazon.com
• General Manager, AWS EKS
• Launched EKS – June 2018
• Working on Kubernetes since before 1.0
• Kubernetes SIG Scalability Founder
• Former CNCF Governing Board Member
• @bobwise on Kubernetes Slack
• @countspongebob on GitHub / Twitter

3
Jevon’s Paradox

4
Good intentions… painful result
Spiral to Slowness
Org gridlock
Hand-crafted
Deploy
Failed use
reports
Re-Install
Previous
RCA—
shame
Try Again
Lengthen soak test
Start
manual
sign-
offs
Larger
release
More Manual
tests
Only roll-
forward possible
Make Stage
a full replica
Test cycle time
increases
Even Larger
Release
Impact of
failure much
wider
Exec sign-off
before release
Zero-failure
policy
implemented
Small group
of superstars
willing to risk
change/install
Team
discordLengthen
planning
cycle
Blame the
Monolith!!!
Great
team

5
Motivating Trends
• Leadership frustration over lack of velocity.
• Massive and widening gap between high performance and average
performance software orgs.
• Desire to constrain sprawl, use fewer, better tools and approaches.
• Engineering orgs wanting needing to modernize for retention and
recruiting.

6
Teams that practice CD ship (not just build) more code
faster, and with more confidence
Source: Puppet 2017 State of DevOps Report
5x
Lower change
failure rate
440x
Faster from
commit to deploy
46x
More frequent
deployments
44%
More time spent on
new features & code

7
Easier than ever to make real…
Awesome Public Cloud
Infrastructure
Cloud Native
Tooling
Team dynamics:
Hiring.
Morale.
Career.
Fun.

8
The Perfect Container Storm
• Standardized format + immutable approach = perfect for CI and CD.
• Easy to use tooling made it approachable for early adopters.
• Tooling made it easy to start with something small and extend it.
• Efficiency of the approach removed financial friction.
• Adoption led to contribution, improvement, and more adoption.
• …but container orchestrators made it viable at scale.

9
Customer Strategies
• Focus on modern operations (CD) as the chokepoint to
velocity over development improvements (Agile dev and CI).
• Container orchestration key to realizing CI and CD and
velocity.
• Operations hygiene as a prelude to microservice re-
architecture: CD + observability + orchestration.

10
Customer Strategies are Evolving
• Central IT teams building platforms.
• Adopting interoperable components from an open ecosystem.
• Participation in open source and upstreaming “Farm to Table Open
Source”: Better security, more control, less risk.
• Owning and controlling software supply chain instead of single-vendor
full-stack outsourcing.
• Standardizing on key systems, e.g. Kubernetes as the platform
platform.
• Golden path to velocity to engage adoption: more carrot, less stick.

11
Path to higher velocity…
Virtuous
Low confidence
“CD”
Painful
Rollback
Broken
Deploys
Reduce Size
Increase Auto
Tests
Release
Fix
Redeploy
Smooth
Rollback
Fix
Redeploy Reduce
Size
Increase Auto
Tests
Smaller
Releases
Auto
Rollback
Fix
High confidence
Reduce
Size
Regression
Auto Tests
Manual/
Auto test
Even
Smaller
Releases
Monitor
(publicly)

12
Opinionated Perspective
• High level systems cause developer gridlock and despair if everyone is
forced to use them: Containers have hit the sweet spot.
• Side-by-side vertical choices cause operations despair, complication, and
inefficiency: do force one kind of turtle at the bottom.
• Automate services before building microservices. Don’t blame the
monolith!
• Entry to a cluster for deploying services should be gitops and CD tooling
NOT kubectl.
• Developers and operators wanting to ssh to nodes and containers is
signal that the tooling is not adequate, not that they are special
snowflakes.

13
Provocative Thoughts from wisebob@
Distro is a dirty word: it implies a proprietary vendor-maintained fork is
needed. Kubernetes learned this lesson from Openstack: Trunk must be
usable without forking. Please don’t call EKS a “distro”!
Every service should be treated like a micro service and should be the
right size. Most monoliths should be slowly refactored – but only if there is
actual benefit. Search all docs for word “micro” and remove.
CI/CD… Red flag for doing CI and not CD. Search all docs and separate.
CI is easy, CD is hard. CI is dev, CD is ops.

14
EKS Journey

15
2018 - Amazon EKS1. June 5: Amazon Elastic Container Service for Kubernetes Now Generally Available
2. June 28: Amazon EKS is HIPAA Eligible
3. July 10: Amazon EKS AMI Build Scripts Available on GitHub
4. July 26: Amazon VPC CNI Plugin Version 1.1
5. August 23: New Amazon EKS-optimized AMI and CloudFormation Template for Worker Node Provisioning
6. August 23: Amazon EKS Supports GPU-Enabled EC2 Instances
7. August 30: Introducing Amazon EKS Platform Version 2
8. August 30: Amazon EKS Supports Horizontal Pod Autoscaling with Custom Metrics
9. September 5: Amazon EKS Available in Ireland
10. September 21: Amazon EKS Simplifies Cluster Setup with update-kubeconfig CLI Command
11. October 12: Amazon EKS Enables Support for Kubernetes Dynamic Admission Controllers
12. October 18: Amazon VPC CNI Plugin Version 1.2.1
13. October 25: Amazon EKS now supports additional VPC CIDR blocks
14. November 7: Amazon EKS Available in Ohio Region
15. November 20: Amazon EKS Adds ALB Support with AWS ALB Ingress Controller
16. November 27: AWS Announces New Container Products in AWS Marketplace
17. November 28: AWS Fargate, Amazon EKS, and Amazon ECS now integrate with AWS Cloud Map
18. November 28: Introducing AWS App Mesh - Service Mesh for Microservices on AWS
19. December 12: Amazon EKS Adds Managed Cluster Updates and Support for Kubernetes Version 1.11
20. December 19: Amazon EKS Available in Frankfurt, Singapore, Sydney, and Tokyo AWS Regions
21. January 9: Amazon EKS Available in Seoul Region
22. January 16: Amazon EKS Announces 99.9% Service Level Agreement
23. January 21: Amazon EKS Achieves ISO and PCI Compliance
24. February 13: Amazon EKS Available in Mumbai, London, and Paris AWS Regions
25. February 13: Amazon EKS Releases VPC CNI plugin v1.3.2 with Enhancements for P3dn Instances
August 30: Amazon EKS Supports Horizontal Pod Autoscaling with Custom Metrics
November 20: Amazon EKS Adds ALB Support with AWS ALB Ingress Controller
December 12: Amazon EKS Adds Managed Cluster Updates and Support for
Kubernetes Version 1.11
October 12: Amazon EKS Enables Support for Kubernetes Dynamic Admission Controllers

16
2019 - Amazon EKS
1. January 9: Amazon EKS Available in Seoul Region
2. January 16: Amazon EKS Announces 99.9% Service Level Agreement
3. January 21: Amazon EKS Achieves ISO and PCI Compliance
4. February 13: Amazon EKS Available in Mumbai, London, and Paris AWS Regions
5. February 13: Amazon EKS Releases VPC CNI plugin v1.3.2 with Enhancements for P3dn Instances
6. March 19: Private API endpoints
7. March 25: EBS CSI Driver Beta published on github (OSS)
8. March 27: EKS App Mesh Controller and App Mesh GA
9. March 27: EKS supports launch of deep learning containers
10. March 27: Windows worker nodes/Windows containers preview
11. March 28: Kubernetes 1.12
12. 3/29 - EKS Optimized AMI supports CUDA10
13. April 2: EFS and FSX for Lustre CSI driver alpha published on github (OSS), EBS driver in Beta
14. April 4: Control plane logs in cloudwatch: audit, API server, scheduler, and controller logs
15. April 10 : Non-RFC1918 support – CGNAT
16. April 15: CNI 1.4 with 3 new features, and 30+ minor enhancements and bug fixes
17. April 19: IAM Authenticator 0.4 – bug fixes and MFA token caching
18. April 25: EKS Deep learning benchmark utility published OSS on github
19. April 30: Kubeflow on AWS doc PR merged
20. April 30: eksctl 1.31: nodegroup enhancements, AMI search enhancements, aws-iam-authenticator update
21. May 6: Upstream improvements to Escalator merged
22. May 9: Support for Public IP space in VPC
23. May 14 - Simplified cluster authentication with get-token command
24. May 14 - eksctl supported as official CLI for EKS )
25. May 17 - EKS is SOC compliant
February 2019: US-East & West, Ireland, Ohio, Frankfurt, Singapore, Sydney,
Tokyo, Seoul, Mumbai, London, Paris
March 27: EKS App Mesh Controller
April 4: Control plane logs in CloudWatch: audit, API server, scheduler, and controller logs
Recent: Windows Preview, ARM Preview, Kubeflow on AWS, Escalator enhancements

17
EKS Major Themes
• Security and stability.
• Feature priority for big IT platform builders.
• APIs are for platform builders and GitOps.
• Working upstream on providers and plugins for decoupling from
core Kubernetes without needing to fork. The goal is to help
Kubernetes be smaller and better.
• Networking is both hard and critical: lots of CNI updates, and
more to come.
• EKS is an ML platform: Instances, upstream, benchmarking,
autoscalers, tensorflow, kubeflow.

18
EKS Fun Facts
• Cellular architecture for blast radius management.
• Built on customer-facing services (EC2, NLB, S3, etc).
• Etcd maintainers.
• Open sourced by our team: CNI, CSI drivers, Packer/AMI.
• Eksctl (our CLI) is a community project partnering with Weaveworks.
• Eksctl: 64 contributors, 1228 stars, 190 forks.
• Our roadmap is open source

19
Special open source roadmap slide callout

20
Cognitive dissonance is the mental discomfort (psychological stress)
experienced by a person who holds two or more
contradictory beliefs, ideas, or values.

21
ECS and EKS
• Very happy customers for both systems.
• Increasing adoption for both systems.
• Increasing investment for both systems.
• Coke + Sprite / Mysql + Postgres.

22
AppMesh and Istio
• We love your Istio deployments on EKS: we prioritized Istio support in
our early roadmap.
• We would love you to use App Mesh.
• App Mesh scope is wider than containers.
• BTW…both are control planes for Envoy.

23
R E K O G N I T I O N
I M A G E
P O L L Y T R A N S C R I B E T R A N S L A T E C O M P R E H E N D L E XR E K O G N I T I O N
V I D E O
F O R E C A S TT E X T R A C T P E R S O N A L I Z E
VISION SPEECH LANGUAGE CHATBOTS FORECASTING RECOMMENDATIONS
Amazon
SageMaker Ground Truth Notebooks Algorithms + Marketplace
Reinforcement
Learning
Training Optimization Deployment Hosting
EC2 P3
& P3dn
EC2
C5
FPGAs Greengrass
Elastic
inference
FRAMEWORKS INTERFACES INFRASTRUCTURE
Inferentia
EC2
G4
EKS and AWS ML Ecosystem

24
Closing emphasis…
• AWS believes deeply in customer choice both horizontally and
vertically and providing both assembled solutions and modular
components.
• More AND less OR.
• Building code with us in open source means we manage your code
with our operations teams.
• Interoperability in the long run is based on staying upstream and
not forking.
• We are happy to help upstream even if you aren’t using EKS.

25
Repos of note
https://github.com/aws/containers-roadmap
https://github.com/aws-samples/aws-eks-deep-learning-benchmark
https://github.com/aws-samples/machine-learning-using-k8s
https://github.com/aws-samples/eks-workshop
https://github.com/aws/amazon-vpc-cni-k8s
https://github.com/awslabs/amazon-eks-ami
https://github.com/aws/aws-app-mesh-inject
https://github.com/kubernetes-sigs/aws-ebs-csi-driver

26
EKS Partners

Modernizing on EKS (Keynote)- AWS Container Day 2019 Barcelona

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Modernizing on EKS (Keynote)- AWS Container Day 2019 Barcelona

Semelhante a Modernizing on EKS (Keynote)- AWS Container Day 2019 Barcelona (20)

Mais de Amazon Web Services

Mais de Amazon Web Services (20)

Modernizing on EKS (Keynote)- AWS Container Day 2019 Barcelona