Downloaded 243 times
![{
"name": "night",
"cron": "0 0 21 * * *",
"description": "Switch to half capacity at night",
"desiredCapacity": 2,
"appScaleTemplates": [
{
"app": "demo",
"replicationControllerScaleTemplates": [
{
"replicationController": "*",
"replicas": 1
}
]
}
]
}
scalerctl create nighttime.json](https://image.slidesharecdn.com/kubernetes-automation-devoxx-160608163652/85/Kubernetes-automation-in-production-71-320.jpg)
Uploaded byPaul Bakker
Kubernetes automation in production
The document outlines Kubernetes automation, focusing on its features like container orchestration, service management, and load balancing. It discusses the architecture of Kubernetes, including nodes, pods, and services, and highlights deployment strategies such as blue-green deployment. Additionally, it covers scaling techniques for Kubernetes clusters and the management of data stores within this environment.
More Related Content
Similar to Kubernetes automation in production
Kubernetes automation in production
- 1.
- 2. @pbakker Paul Bakker Software architectat Luminis Technologies
- 3. @pbakker Paul Bakker Software architectat Luminis Technologies
- 4. Why Kubernetes • RunDocker in clusters • scheduling containers on machines • networking • storage • automation
- 5.
- 6.
- 7.
- 8. nginx web files Pod • May containmultiple containers • Lifecycle of these containers bound together • Containers in pod see each other on localhost • Env vars for services pod REDIS_SERVICE_HOST=10.201.159.165 REDIS_PORT_6379_TCP_PORT=6379 Container Container
- 9. Networking • We runmany pods on a single machine • Pods may expose the same ports • How to avoid conflicts!?
- 10. Dynamic IP addresses • Eachpod gets a virtual IP • Ports not shared with other pods
- 11. pod pod Docker container Docker container Docker container Service Services Fixed, virtual IPaddress Dynamic IP address Dynamic IP address
- 12. Multi component deployments • Eachcomponent deployed as a pod • Individually update and scale pods • Use services for component communication
- 13. Multi component deployments frontend backend service 1 backend service2 Redis pod pod pod pod backend service 1 backend service 1 backend service 1 backend service 2 backend service 2 backend service 2 s e r v i c e s e r v i c e s e r v i c e
- 14. Multi component deployments frontend backend service 1 backend service2 Redis pod pod pod pod backend service 1 backend service 1 backend service 1 backend service 2 backend service 2 backend service 2 s e r v i c e s e r v i c e s e r v i c e application
- 15. Multi component deployments frontend backend service 1 backend service2 Redis pod pod pod pod backend service 1 backend service 1 backend service 1 backend service 2 backend service 2 backend service 2 s e r v i c e s e r v i c e s e r v i c e component / service
- 16.
- 17. kubectl kubectl create -fmy-rc.yml kubectl create -f my-service.yml
- 18. apiVersion: v1 kind: ReplicationController metadata: name:nginx spec: replicas: 3 selector: app: nginx template: metadata: name: nginx labels: app: nginx spec: containers: - name: nginx image: nginx ports: - containerPort: 80
- 19. apiVersion: v1 kind: ReplicationController metadata: name:nginx spec: replicas: 3 selector: app: nginx template: metadata: name: nginx labels: app: nginx spec: containers: - name: nginx image: nginx ports: - containerPort: 80 On how many nodes should this run?
- 20. apiVersion: v1 kind: ReplicationController metadata: name:nginx spec: replicas: 3 selector: app: nginx template: metadata: name: nginx labels: app: nginx spec: containers: - name: nginx image: nginx ports: - containerPort: 80 On how many nodes should this run? Describes our Docker container Ports, storage needs, etc.
- 21. apiVersion: v1 kind: ReplicationController metadata: name:nginx spec: replicas: 3 selector: app: nginx template: metadata: name: nginx labels: app: nginx spec: containers: - name: nginx image: nginx ports: - containerPort: 80 On how many nodes should this run? Labels, this (loosely) couples controllers, pods and services together Describes our Docker container Ports, storage needs, etc.
- 22.
- 23.
- 24. HTTP load balancing •Expose Kubernetes services to the outside world • SSL offloading • Gzip • Redirects
- 25. Kubernetes ingress • Builtin support for GCE load balancers • Future support for extensions (not quite there yet) • What about your own environment!?
- 26. Using a custom loadbalancer • Use Ha-proxy in front of Kubernetes • Configure Ha-proxy dynamically • The same works for nginx, apache…
- 27. pod pod Docker container Docker container Docker container Service Dynamic IP address Dynamic IP address Loadbalancer node ha-proxy HTTPS SSL offloading
- 28. pod pod Docker container Docker container Docker container Service Dynamic IP address Dynamic IP address Loadbalancer node ha-proxy HTTPS A W S E L B SSL offloading
- 29. pod pod Docker container Docker container Docker container Service Dynamic IP address Dynamic IP address Loadbalancer node ha-proxy HTTPS A W S E L B Virtual private network
- 30. How does ha-proxyknow about our services? • Ha-proxy uses a static config file • Auto-generate it based on data in etcd • Confd
- 31.
- 32. Using the API •/v1/namespaces/mynamespace/pods • /v1/namespaces/mynamespace/services • /v1/namespaces/mynamespace/replicationcontrollers REST API that gives access to everything
- 33. Client libraries • AmdatuKubernetes OSGi • Amdatu Kubernetes Go • Clojure, Node, Python etc… kubernetes.listNodes().subscribe(nodes -> { nodes.getItems() .forEach(System.out::println); }); pods, err := kubernetes.ListPods(TEST_NAMESPACE) if err != nil { panic(err) } for _,pod := range pods.Items { log.Println(pod.Name) } Java Go
- 34. Blue-green deployment • Deploymentwithout downtime • Only one version is active at a time • Rolls back on failed deployment
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46. Kubernetes API Deployer podpodpod pod GET /health CreateRC service Creates The Deployer
- 47. Kubernetes API etcd Deployer podpodpod pod GET /healthCreate RC confd Watch Switch Load Balancer Backend service Creates The Deployer
- 48. Kubernetes API HAProxy etcd Deployer podpodpod pod GET /health CreateRC generate config confd Watch Switch Load Balancer Backend service Creates The Deployer
- 49.
- 50.
- 51.
- 52. Kubernetes API Deployer podpodpod pod 3- GET /health1- Create RC service 2- Creates
- 53. Kubernetes API etcd Deployer podpodpod pod 3- GET/health 1- Create RC confd 5- Watch 4- Switch Load Balancer Backend service 2- Creates
- 54. Kubernetes API HAProxy etcd Deployer podpodpod pod 3- GET /health1- Create RC 6- generate config confd 5- Watch 4- Switch Load Balancer Backend service 2- Creates
- 55. Amdatu Kubernetes Deployer • Kubernetesdeployment orchestration • Load balancer configuration • Blue-green deployment • Apache licensed • Go
- 56. { "deploymentType": "blue-green", "namespace": "default", "useHealthCheck":true, "newVersion": "#", "appName": "cloudrti-demo", "replicas": 2, "frontend": "cloud-rti-demo.amdatu.com", "podspec": {} }
- 57. Amdatu Deploymentctl • UIfor setting up deployments • Deployment history • Webhooks for triggering from external events • OSGi / Vertx / Angular 2
- 58.
- 59. Build / deploypipelines Build Server Docker Hub builds image alpha Deployer webhook deploys
- 60.
- 61. Kubernetes node How toscale a Kubernetes cluster?
- 62. Kubernetes node pod podpod pod pod pod How to scale a Kubernetes cluster?
- 63. How to scalea Kubernetes cluster? Kubernetes node pod pod pod pod pod pod pod pod pod pod pod pod
- 64. How to scalea Kubernetes cluster? Kubernetes nodeKubernetes nodeKubernetes node pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod
- 65. How to scalea Kubernetes cluster? Kubernetes nodeKubernetes nodeKubernetes node pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod
- 66. How to scalea Kubernetes cluster? Kubernetes nodeKubernetes node pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod pod
- 67. How to scalea Kubernetes cluster? Kubernetes nodeKubernetes nodeKubernetes node
- 68. Scaling up 1. UseAWS API to start new nodes (ScalingGroup) 2. Cloud-init to register node to Kubernetes cluster
- 69. Scaling down 1. Setnode to “unschedulable” 2. Drain node (relocate pods to other machines) 3. Remove node from Kubernetes 4. Use AWS API to terminate nodes (ScalingGroup)
- 70. Amdatu scalerd • CLIto add/remove nodes to a cluster • Node draining to prevent downtime • Scheduled automated scaling
- 71. { "name": "night", "cron": "00 21 * * *", "description": "Switch to half capacity at night", "desiredCapacity": 2, "appScaleTemplates": [ { "app": "demo", "replicationControllerScaleTemplates": [ { "replicationController": "*", "replicas": 1 } ] } ] } scalerctl create nighttime.json
- 72. How and whereto run these tools? • In Kubernetes of course! • Bootstrap using kubectl scripts
- 73.
- 74.
- 75. Datastores in Kubernetes •Kubernetes does have persistent volumes • Most data stores require lots of tuning • … don’t auto scale • … require manual steps to configure cluster
- 76.
- 77. • Fully managedKubernetes • Centralised logging • Application / cluster monitoring
- 82.