gcp / gke / k8s microservices

Size: px

Start display at page:

Download "gcp / gke / k8s microservices"

Noel Poole
6 years ago
Views:

1 gcp / gke / k8s microservices managing microservices with kubernetes Austin GCPUG Lou Scalpati CTO RxWiki

2 microservices What are Microservices generally REST APIs returning json organized around function: a user service, crud for db app or a url shortening service small units of an app but are standalone Why Microservices? modular easy to deploy scales independently Reduces maintenance issues uncouples components of your app - changes can be deployed without having to test entire codebase reusable usually a single developer or small team can create / manage mixed language environment

monolithic vs microservices https://www.safaribooksonline.

3 monolithic vs microservices

4 the 12 Factor App (or 12 factor microservice) I. Codebase (git) One codebase tracked in revision control, many deploys II. Dependencies (vendoring) Explicitly declare and isolate dependencies III. Config (docker) Store config in the environment IV. Backing services (docker/k8s) Treat backing services as attached resources V. Build, release, run (docker/k8s) Strictly separate build and run stages VI. Processes (docker/k8s) Execute the app as one or more stateless processes VII. Port binding (docker/k8s) Export services via port binding VIII. Concurrency (docker/k8s) Scale out via the process model IX. Disposability (docker) Maximize robustness with fast startup and graceful shutdown X. Dev/prod parity (docker/k8s) Keep development, staging, and production as similar as possible XI. Logs (docker/k8s) Treat logs as event streams XII. Admin processes (k8s) Run admin/management tasks as one-off processes

5 what is Kubernetes (k8s) What it does application configuration service Discovery managing Updates monitoring containers PAAS that manages your application deployment and operations Commonly used components pods deployments replicasets /replication controllers services labels (tag) driven

6 k8s Pods and Services Pods tightly coupled containers scaled together shared: Namespace Volumes IP short life span - spin up and down quickly Services defines a logical set of pods defines access policy to pods really a microservice Targets pods by label selector base unit for service discovery More permanent than pods

7 the architecture (the obligatory diagram) internet Service Load Balancer Service Service Pod Pod Pod Pod Pod Pod

8 deployments and ReplicaSets Deployments combines pods and scaling policies declarative updates for Pods and Replica Sets describe the desired state deployment controller will: change the actual state to the desired state Control rate of change Rollback to an earlier Deployment revision History ReplicaSets the next-generation Replication Controller works as part of a deployment can be used standalone (but why?)

9 creating a deployment apiversion: extensions/v1beta1 kind: Deployment metadata: name: nginx-deployment spec: replicas: 3 template: metadata: labels: app: nginx spec: containers: - name: nginx image: nginx:1.7.9 ports: - containerport: 80 create a deployment $ kubectl create -f docs/user-guide/nginx-deployment.yaml --record deployment "nginx-deployment" created get deployment status $ kubectl get deployments NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE nginx-deployment s get ReplicaSet Status $ kubectl get rs NAME DESIRED CURRENT AGE nginx-deployment s

10 fun with deployments (updates and rollouts) updating a deployment (rollout) $ kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 deployment "nginx-deployment" image updated or edit the yaml (rollout) and $ kubectl edit deployment/nginx-deployment deployment "nginx-deployment" edited status of deployment (rollout) $ kubectl rollout status deployment/nginx-deployment deployment nginx-deployment successfully rolled out shows the status (new and old) $ kubectl get rs NAME DESIRED CURRENT AGE nginx-deployment s nginx-deployment s

11 deployment history check history $ kubectl rollout history deployment/nginx-deployment deployments "nginx-deployment": REVISION CHANGE-CAUSE 1 kubectl create -f docs/user-guide/nginx-deployment.yaml --record 2 kubectl set image deployment/nginx-deployment nginx=nginx: kubectl set image deployment/nginx-deployment nginx=nginx:1.91

12 deployment history (details of a point in time) $ kubectl rollout history deployment/nginx-deployment --revision=2 deployments "nginx-deployment" revision 2 Labels: app=nginx pod-template-hash= Annotations: kubernetes.io/change-cause=kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 Containers: nginx: Image: nginx:1.9.1 Port: 80/TCP QoS Tier: cpu: BestEffort memory: BestEffort Environment Variables: <none> No volumes.

13 roll back (this is why to use deployments) undo! $ kubectl rollout undo deployment/nginx-deployment deployment "nginx-deployment" rolled back roll back to a point in time! $ kubectl rollout undo deployment/nginx-deployment --to-revision=2 deployment "nginx-deployment" rolled back Note: Kubectl rolling update updates Pods and Replication Controllers in a similar fashion. But Deployments are recommended, since they are declarative, server side, and have additional features, such as rolling back to any previous revision even after the rolling update is done.

14 load balancing options GCP network load balancer automatic defined in service connects directly to service layer 3 no SSL GLBC k8s L7 Load balancer Still beta Layer 7 configure ingress objects does not clean up all network resources no SSL (?? ingress object) GCP HTTP/HTTPS Load Balancer manual config SSL Certificate process?? nginx defacto standard reverse proxy supports SSL layer 7 needs configuration easy to deploy haproxy versatile L3,4,5,6,7 designed for network proxy what I use many others

15 resources the 12 factors: K8s services: k8s deployments: k8s microservices course (free):

Cloud-Native Applications. Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0

Cloud-Native Applications. Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0 Cloud-Native Applications Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0 Cloud-Native Characteristics Lean Form a hypothesis, build just enough to validate or disprove it. Learn