Introduction to Containers w/ Docker, Kubernetes & OpenShift, Module 1: Containers and Containerization

0.0(0)
studied byStudied by 4 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/165

flashcard set

Earn XP

Description and Tags

https://docs.google.com/document/d/1LJi_RsDTZJ196pkxBzMh6fEIV4sxSzNTuQFL7xXpfTw/edit?tab=t.rp48rl6enokl

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

166 Terms

1
New cards

What’s cloud-native?

application always in a cloud from start

2
New cards

What are upsides of cloud-native applications?

often scalable/resilient, easy to update

3
New cards

What do cloud-native applications use?

  • containers

  • microservices

  • managed cloud services

4
New cards

What does cloud refer to (in computing)?

a big network of remote servers globally used to store/manage data IO local servers/PCs

5
New cards

What’s a remote server?

computer system housed in a professional data center

6
New cards

Define “scalable”?

grow/handle works easily without breaking

7
New cards

Define “dynamic”?

everchanging, adaptive, flexible

8
New cards

What’s a hybrid cloud-friendly software?

software working in both private and public cloud environments

9
New cards

What’s a container (in computing)?

isolated software package with anything to run an application, (e.g. code, libraries, system tools)

10
New cards

What’s 1 crucial thing in cloud-native’s approach?

containers

11
New cards

Define “standardization”?

to create/use consistent rules for things to be similar

12
New cards

What improves shipping efficiency a bit?

standardization

13
New cards

Define “logistic”?

to manage how resources are acquired/stored/transported elsewhere

14
New cards

Define “dependency” (in softwares)?

external libraries/tools programs use to work properly

15
New cards

What’s a digital container technology?

a way to package software and its dependencies into containers

16
New cards

What are containerization softwares

software creates/runs containers with their dependencies to run consistently anywhere

17
New cards

Define “encapsulate”.

to wrap/contain

18
New cards

Define “blocker” (in software engineering).

issue/factor blocking developper

19
New cards

What’s a staging environment?

(or just staging) final testing environment that exactly act as production environment for prior launch

20
New cards

What’s a production environment/”prod”/live stage?

"live" stage where product or application actually accessible to users

21
New cards

In traditional environments, we can’t?

isolate apps, allocate memories for apps on physical servers.

22
New cards

What environment is this depicting?
In traditional environments, we can’t isolate apps, allocate memories for apps on physical servers.”

Traditional Deployment or Bare Metal server

23
New cards

What’s a Traditional Deployment?

old way to install applications directly to physical servers

24
New cards

What happens if servers are often underused?

poor investment return

25
New cards

What’s a investment return?

(investment in servers/IT infrastructure): companies buy to maintain servers, but if they aren’t used much = low investment return

26
New cards

What do Traditional deployments need make it a downside.

hardware, time, money, personnel and costly maintenance

27
New cards

Are Tradiational deployments

unportable in many environments and operating systems

28
New cards

What’s a operating systems?

software supporting device basic functions (e.g. scheduling tasks, executing applications)

29
New cards

What’s a container engine?

(like Docker) software running containers in system

30
New cards

Define “to virtualize”.

to create a thing’s virtual version IO physical

31
New cards

T or F? Container engines virtualize operating system.

T

32
New cards
33
New cards

What are a platform-independent container’s upsides?

  • fast

  • isolated

  • portable

  • secure

  • need less memory space

34
New cards

Being _________________, they can run on Windows, Linux, or Mac OS.

Being platform-independent, they can run on Windows, Linux, or Mac OS.

35
New cards

How can containers help us?

  • quickly make applications

  • less deployment time/costs

  • better resource utilization (CPU, memory)

  • deploy code in applications

36
New cards

What issues of containers?

  • Server security is issue if its operating system is affected.

  • maybe overwhelmed by many containers

  • converting monolithic legacy applications can be

  • Developers can struggle right-sizing containers for certain scenarios.

37
New cards

What are popular container vendors today?

  • Docker: robust platform, most used container platform

  • Podman: daemonless container engine more secure than Docker

  • daemonless: software not need constant background run service (daemon) to manage containers

  • LXC: preferred by developers for data-intensive applications

  • Vagrant: highest isolation lvl on running physical machine

38
New cards

Define “daemonless“.

software not needing constant background run service (daemon) to manage

39
New cards

Define “daemon“.

constant background run to handle tasks

40
New cards
41
New cards
42
New cards
43
New cards
44
New cards
45
New cards
46
New cards
47
New cards
48
New cards
49
New cards
50
New cards
51
New cards
52
New cards
53
New cards
54
New cards
55
New cards
56
New cards
57
New cards
58
New cards
59
New cards
60
New cards
61
New cards
62
New cards
63
New cards
64
New cards
65
New cards
66
New cards
67
New cards
68
New cards
69
New cards
70
New cards
71
New cards
72
New cards
73
New cards
74
New cards
75
New cards
76
New cards
77
New cards
78
New cards
79
New cards
80
New cards
81
New cards
82
New cards
83
New cards
84
New cards
85
New cards
86
New cards
87
New cards
88
New cards
89
New cards
90
New cards
91
New cards
92
New cards
93
New cards
94
New cards
95
New cards
96
New cards
97
New cards
98
New cards
99
New cards
100
New cards