Share
Embed
Modernizing microservices on Kubernetes with Cloud Run for Anthos/GKE
How can you make your existing microservices apps on Kubernetes to make use of Knative (https://knative.dev) to take advantage of better autoscaling, load balancing, scale-to-zero and many other capabilities on a Google Anthos (https://anthos.dev) cluster.
Presented at Google’s Anthos Day @ KubeCon 2019 San Diego, CA by Ahmet Alp Balkan and Jason (Jay) Smith.
Ahmet Alp Balkan
November 18, 2019
Transcript
41 slides
-
Modernizing microservices with Cloud Run for Anthos a.k.a. how to
get serverless in your Kubernetes cluster Anthos Day – KubeCon 2019, San Diego Monday, November 18, 2019 -
Ahmet Alp Balkan Developer Advocate @ahmetb Jason (Jay) Smith Customer
Engineer @thejaysmith -
Anthos Google Cloud Platform On-Premises Public Cloud Anthos GKE deployed
on VMware Hub / Connect Anthos Config Management Anthos Service Mesh GKE Anthos GKE deployed on AWS Kubernetes Cluster GCP Marketplace Anthos Migrate ??? -
Anthos Google Cloud Platform On-Premises Public Cloud Anthos GKE deployed
on VMware Hub / Connect Anthos Config Management Anthos Service Mesh GKE Anthos GKE deployed on AWS Kubernetes Cluster GCP Marketplace Anthos Migrate Cloud Run on Anthos -
Serverless Operational Model Programming Model No infra management No ops
for scaling Managed security Pay per usage (request, etc) Service-based Request/event driven Stateless applications / -
Serverless > Functions Compute Data Analytics ML & AI Database
& Storage Smart assistants & chat DevOps Messaging -
Container image to production URL in a few seconds Run
services in any language or framework Fully-managed, rapid autoscaling, pay per request Cloud Run -
✔ Legacy application deployment ✔ Fully managed, rapid autoscaling, scale-to-zero
✔ Production-ready, secured (HTTPS) endpoint What if you want these on your Kubernetes cluster? What we just saw -
Serverless, on your terms Cloud Run (fully managed) • Serverless
dev/operator experience • Runs on Google’s infrastructure • Pay-per-request Cloud Run for Anthos • Serverless developer experience • Runs in your Anthos/GKE cluster next to your Kubernetes workloads • Customizable/pluggable for your needs -
GKE on GCP GKE on-prem Google infra Cloud Run for
Anthos Knative GKE (Kubernetes) Knative API UI CLI YAML Cloud Run Developer & Operator -
Knative Open source API and implementation that codifies "serverless on
Kubernetes". Adds capabilities to Kubernetes to run stateless microservices more effectively. Heavily customizable and pluggable. Managed for you, with Cloud Run for Anthos. Has a strong community, backed by Google, Red Hat, IBM, SAP and other contributors. knative.dev knative.dev -
Kubernetes Memory/CPU based autoscaling (slow) Knative Rapid, request-oriented autoscaling Handles
traffic spikes Knative enhances Kubernetes Autoscaling More: https://ahmet.im/blog/knative-better-kubernetes-networking/ -
Kubernetes N/A Knative Scale application to 0, if no requests
coming Activate (0→1) on the next request Knative enhances Kubernetes Scale to zero More: https://ahmet.im/blog/knative-better-kubernetes-networking/ -
Kubernetes Connection-based load balancing Knative Per-request load balancing Traffic splitting
(blue/green deployments) Knative enhances Kubernetes Load Balancing More: https://ahmet.im/blog/knative-better-kubernetes-networking/ -
What we just saw ✔ Same developer/ops experience as the
fully-managed Cloud Run ✔ Knative installation, managed for you by Cloud Run for Anthos on GKE ✔ Traffic splitting, without writing YAML files ✔ Knative is still Kubernetes. -
✓ Stateless applications (microservices, frontends, event handlers, queue processing) ✓
Listens on a port number with HTTP or gRPC. ✓ Ideally, doesn't take too long to start up and process requests. What’s good with Cloud Run? -
apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1
selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 -
apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1
selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 -
apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1
selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 -
apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1
selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 -
apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1
selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 -
apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello
tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1 selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service -
apiVersion: v1 kind: Service metadata: name: hello-web labels: app: hello
tier: web spec: type: ClusterIP selector: app: hello tier: web ports: - port: 80 targetPort: 8080 apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1 selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/google-samples/hello-app:1.0 resources: limits: cpu: 100m memory: 256Mi Kubernetes Deployment Kubernetes Service -
Knative Service = Kubernetes Deployment + Kubernetes Service apiVersion: apps/v1
kind: Deployment metadata: name: hello-web spec: replicas: 1 selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/[...] resources: limits: cpu: 100m memory: 256Mi apiVersion: serving.knative.dev/v1alpha1 kind: Service metadata: name: hello-web spec: template: spec: containers: - image: gcr.io/[...] resources: limits: cpu: 100m memory: 256Mi -
Knative Service = Kubernetes Deployment + Kubernetes Service apiVersion: serving.knative.dev/v1alpha1
kind: Service metadata: name: hello-web spec: template: spec: containers: - image: gcr.io/[...] resources: limits: cpu: 100m memory: 256Mi apiVersion: apps/v1 kind: Deployment metadata: name: hello-web spec: replicas: 1 selector: matchLabels: app: hello tier: web template: metadata: labels: app: hello tier: web spec: containers: - name: main image: gcr.io/[...] resources: limits: cpu: 100m memory: 256Mi -
Knative eventing Benefits • Declaratively bind between event producers and
deployed services • Scales from just few events to live streams • Custom event pipelines to connect with your own existing systems -
Wrap-up: Cloud Run on Anthos • Easier deployment and operations
for microservices. • Increased productivity and velocity. • Enable your developers and operators. -
Thanks! Resources • cloud.run ◦ anthos.dev • knative.dev ◦ github.com/ahmetb/cloud-run-faq
• gitlab.com/serverlessjay/cloud-run-eventing ◦ knative.tips