seulcoding

ch4. Replication and other controllers: deploying managed pods 4.5. Running pods that perform a single completable task 소챕터들 4.1 keeping pods healthy 4.2. introducing replicationcontrollers 4.3. using replicasets instead of replicationcontroller 4.4. running exactly one pod on each node with daemonset 4.5. running pods that perform a single completable task 4.6. scheduling jobs to run periodical..

ch4. Replication and other controllers: deploying managed pods 4.4. Running exactly one pod on each node with daemonsets 소챕터들 4.1 keeping pods healthy 4.2. introducing replicationcontrollers 4.3. using replicasets instead of replicationcontroller 4.4. running exactly one pod on each node with daemonset 4.5. running pods that perform a single completable task 4.6. scheduling jobs to run periodica..

ch4. Replication and other controllers: deploying managed pods 4.3 Using Replicasets instead of replicationController 소챕터들 4.1 keeping pods healthy 4.2. introducing replicationcontrollers 4.3. using replicasets instead of replicationcontroller 4.4. running exactly one pod on each node with daemonset 4.5. running pods that perform a single completable task 4.6. scheduling jobs to run periodically..

ch4. Replication and other controllers: deploying managed pods 소챕터들 4.1 keeping pods healthy 4.2. introducing replicationcontrollers 4.3. using replicasets instead of replicationcontroller 4.4. running exactly one pod on each node with daemonset 4.5. running pods that perform a single completable task 4.6. scheduling jobs to run periodically or once in the future 4.2 Introducing replicationcontr..

ch4. Replication and other controllers: deploying managed pods 소챕터들 4.1 keeping pods healthy 4.2. introducing replicationcontrollers 4.3. using replicasets instead of replicationcontroller 4.4. running exactly one pod on each node with daemonset 4.5. running pods that perform a single completable task 4.6. scheduling jobs to run periodically or once in the future This chapter covers Keeping pods..

03. Pods: running containers in Kubernetes Introducing pods pod is a co-located group of containers and represents the basic building block in Kubernetes container를 직접 띄우는 대신에 pod of containers로 배포하게 된다. 항상 하나의 node 위에서만 뜸 (ex. 두 개의 노드에서 한 pod가 같이 뜰수 없음) 왜 pod가 필요할까? 왜 pod가 필요할까? 왜 container를 직접 사용하면 안될까? 왜 multiple container를 같이 띄워야할까? 만약 같은 machine 안에서 multiple process를 띄워야 한다고 생각해보자. containe..

2. First steps with Docker and Kubernetes 도커에 대한 기본적인 설명. 도커 사용법을 안다면 생략해도 될듯하다. kubenertes 띄우기: minikube 설치 및 사용법에 대한 설명 minikube나 GKE(Google Kubernetes Engine)으로 설명이 되어있다. GKE는 GKE Quickstart를 따라하면 됨. google은 12 month free trial를 제공하지만 이미 사용하였을 경우에는 금액이 청구된다. 이후에 kubernetes 명령어에 사용할 docker image를 빌드해서 push 해주어야한다 app.js에 다음 내용을 추가 const http = require('http'); const os = require('o..

Kubernetes in action 1. Introducing Kubernetes 단일규모의 큰 앱의 다양한 단점 마이크로서비스들의 등장 이들을 오케스트레이션해줄 기능이 필요 적은 수일 경우에는 VM으로도 가능 hardware resources human resources VM 대신 Linux container technologies run multiple services on the same host machine isolating environment like VM; less overhead container는 host의 OS에서 작동하지만 각 프로세스들은 isolated VM과 비교하면? single isolated process running in the host OS, consuming onl..