what is kubernetes?

Kubernetes is just like a tool to help your managing docker containers.
μΏ λ²„λ„€ν‹°μŠ€λŠ” λ„μ»€μ˜ μ»¨ν…Œμ΄λ„ˆλ“€μ„ 관리λ₯Ό λ„μ™€μ£ΌλŠ” νˆ΄μ΄λ‹€.

It is all about automation.
μžλ™ν™”κ°€ ν‚€μ›Œλ“œμž„.

For example, if you have a lot of backend services, if you want to scale up like create a lot more backend services to handle a lot of requests, you will have to do that manually.
예λ₯Ό λ“€μ–΄, ν˜„μž¬ λ‚΄κ°€ λ°±μ—”λ“œ μ„œλ²„λ₯Ό 많이 κ°€μ§€κ³  μžˆλŠ”λ°, 더 λ§Žμ€ μš”μ²­μ„ μ²˜λ¦¬ν•˜κΈ° μœ„ν•΄μ„œ λ°±μ—”λ“œ μ„œλ²„λ₯Ό 쑰금 더 μƒμ„±ν•΄μ„œ 규λͺ¨λ₯Ό ν™•μž₯ν•˜κ³  μ‹Άλ‹€λ©΄, 이 λͺ¨λ“  것듀을 직접 μ²˜λ¦¬ν•΄μ•Όν•œλ‹€.

But with Kubernetes(K8S), all you need is to update one configuration file for different services, or even there might be some K8S UI to use, so bascially K8S w ill do the rest for users.
ν•˜μ§€λ§Œ, μΏ λ²„λ„€ν‹°μŠ€λŠ” λ‹€μ–‘ν•œ μ„œλΉ„μŠ€λ“€μ„ μœ„ν•΄ 단 ν•˜λ‚˜μ˜ ꡬ성 파일만 μ—…λ°μ΄νŠΈν•˜λ©΄ λœλ‹€.
ν˜Ήμ€ μΏ λ²„λ„€ν‹°μŠ€μ˜ UIλ₯Ό μ‚¬μš©ν•˜λ©΄ 되기 λ•Œλ¬Έμ—, 이전에 직접 μ²˜λ¦¬ν•΄μ•Όν•˜λ˜ 것듀을 μΏ λ²„λ„€ν‹°μŠ€κ°€ λŒ€μ‹  ν•΄μ£ΌλŠ” 것과 κ°™λ‹€.

Container & Orchestration

thsee two key factors are very important to understand what Kubernetes is.

Container

what is the differences between Docker and Kubernetes?

Docker

Docker is like a lightweight, standalone, and executalbe package for software.
λ„μ»€λŠ” 쑰금 더 가볍고, 독립적이며, μ†Œν”„νŠΈμ›¨μ–΄λ₯Ό μœ„ν•œ μ‹€ν–‰ νŒ¨ν‚€μ§€λ‹€.
it contains everything a program needs to run, including the code, runtime, libraries, and system tools.
μ½”λ“œ, λŸ°νƒ€μž„, 라이브러리, μ‹œμŠ€ν…œ νˆ΄λ“€μ„ ν¬ν•¨ν•˜μ—¬ ν”„λ‘œκ·Έλž¨μ„ μ‹€ν–‰ν•˜λŠ”λ° ν•„μš”ν•œ λͺ¨λ“ κ²ƒλ“€μ„ λ‹΄κ³  μžˆλ‹€.
Think of it as a shipping container for software, which ensures it will run the same way, regardless of where you deply it.
배에 화물을 싀을 λ•Œ, μ„ μ μš© μ»¨ν…Œμ΄λ„ˆλ“€μ„ 생각해보면 λœλ‹€. 이 μ»¨ν…Œμ΄λ„ˆλ“€μ€ 어디에 λ°°μΉ˜λ˜μ—ˆλŠ”μ§€ 상관 없이 λ™μΌν•œ λ°©μ‹μœΌλ‘œ μ‹€ν–‰λœλ‹€.

Docker ables to run each component in a seperate container with its own
libraries and its own dependencies, all in the same VM and the OS, but within separate environments or containers.
We just had to build the Docker configurartion once, and all our developers could now get started with a simple Docker run command.

DockerλŠ” 각 μ»΄ν¬λ„ŒνŠΈλ₯Ό λ™μΌν•œ VM 및 OS λ‚΄μ—μ„œ λ³„λ„μ˜ ν™˜κ²½ λ˜λŠ” μ»¨ν…Œμ΄λ„ˆ μ•ˆμ—μ„œ 자체 λΌμ΄λΈŒλŸ¬λ¦¬μ™€ μ’…μ†μ„±μœΌλ‘œ μ‹€ν–‰ν•  수 μžˆλ‹€. μš°λ¦¬λŠ” Docker 섀정을 ν•œ 번만 κ΅¬μΆ•ν•˜λ©΄, λͺ¨λ“  κ°œλ°œμžκ°€ κ°„λ‹¨ν•œ Docker run λͺ…λ Ήμ–΄λ‘œ μ‹œμž‘ν•  수 있게 λœλ‹€.


Kubernetes

Imagine, you have lots of these containers(Docker), and you need a way to manage them efficiently.
λ‚΄κ°€ μ—„μ²­λ‚˜κ²Œ λ§Žμ€ μ–‘μ˜ μ»¨ν…Œμ΄λ„ˆλ“€μ„ κ°€μ§€κ³  μžˆλ‹€κ³  μƒμƒν•΄λ³΄μž. κ·Έλ ‡λ‹€λ©΄, 이 λ§Žμ€ μ»¨ν…Œμ΄λ„ˆλ“€μ„ 효과적으둜 λ‹€λ£° 수 μžˆλŠ” 방법이 ν•„μš”ν•  것이닀.
K8S is like a conductor for an orchestra.
(μΏ λ²„λ„€ν‹°μŠ€λŠ” 마치 μ˜€μΌ€μŠ€νŠΈλΌμ—μ„œ μ§€νœ˜μžμ™€ κ°™λ‹€.)
It helps you deploy, scale, and manage containers, ensuring they work harmoniously together.
μΏ λ²„λ„€ν‹°μŠ€λŠ” μ»¨ν…Œμ΄λ„ˆ 배치, ν™•μž₯ 및 관리λ₯Ό 톡해 μ»¨ν…Œμ΄λ„ˆλ“€μ΄ λͺ¨λ‘ μ›ν™œν•˜κ²Œ μž‘λ™ν•˜λ„λ‘ 도와쀀닀.

NameSpace in K8S?

Think of a namespace as a virtual room within the Kubernetes house.
Each room(namespace) allows you to organize different sets of your containers (workloads) separately, so they don't interfere with each other, making management and security easier.

(namespaceλ₯Ό K8S 집에 μžˆλŠ” κ°€μƒμ˜ 방이라 μƒκ°ν•΄λ³΄μž.
각각의 λ°©μ—μ„œ μ»¨ν…Œμ΄λ„ˆ(workload)듀을 μ„œλ‘œ λ‹€λ₯΄κ²Œ ꡬ성할 수 μžˆλ‹€.
κ·Έλ ‡κ²Œν•˜λ©΄, μ„œλ‘œ κ°„μ„­ν•˜μ§€ μ•ŠκΈ° λ•Œλ¬Έμ—, κ΄€λ¦¬ν•˜κ³  λ³΄μ•ˆν•˜κΈ° 더 μ‰¬μ›Œμ§„λ‹€.
κ·Έλž˜μ„œ namespaceλŠ” κ°€μƒμ˜ 곡간이라 μƒκ°ν•˜λ©΄ λœλ‹€.)

Pod in K8S?

Pod is the smallest deployable unit that can run and manage a container or multiple containers.
PodλŠ” ν•˜λ‚˜μ˜ μ»¨ν…Œμ΄λ„ˆ ν˜Ήμ€ μ—¬λŸ¬κ°œμ˜ μ»¨ν…Œμ΄λ„ˆλ₯Ό μž‘λ™μ‹œν‚€κ³  관리할 수 μžˆλŠ” 배포 κ°€λŠ₯ν•œ μ΅œμ†Œ λ‹¨μœ„λ‹€.

Think of it as a single apartment in the K8S house, where one or more containers(Docker file + other codes<FE, BE, DB ...>) live together, sharing storage and network resources. It’s the basic building block of Kubernetes.
Podλ₯Ό μΏ λ²„λ„€ν‹°μŠ€μ˜ 각 μ•„νŒŒνŠΈλΌκ³  μƒκ°ν•΄λ³΄μž.
그럼 ν•˜λ‚˜ ν˜Ήμ€ 두 개 μ΄μƒμ˜ μ»¨ν…Œμ΄λ„ˆλ“€μ΄ μžˆμ„ 것이닀. 이 μ»¨ν…Œμ΄λ„ˆλ“€μ€ νŒŒλ“œ μ•„νŒŒνŠΈμ—μ„œ 같이 μƒν™œν•˜λ©΄μ„œ, storage와 λ„€νŠΈμ›Œν¬ λ¦¬μ†ŒμŠ€λ“€μ„ μ„œλ‘œ κ³΅μœ ν•˜κ²Œ λœλ‹€.
이것이 λ°”λ‘œ μΏ λ²„λ„€ν‹°μŠ€μ˜ 기본적인 κ΅¬μ„±μš”μ†Œλ‹€.


μ—¬μ „νžˆ λͺ¨λ₯΄κ² λŠ” k8s....

profile
πŸ‘©πŸ»β€πŸ’»

0개의 λŒ“κΈ€

Powered by GraphCDN, the GraphQL CDN