Pratique du Shadowing: Kubernetes Explained in 6 Minutes | k8s Architecture - Apprendre l'anglais à l'oral avec la vidéo
Choisissez un mode d'entraînement
Chaque mode ouvre une salle d'entraînement en plein écran.
93 phrases
Si les phrases sont trop courtes ou trop longues, cliquez sur Edit pour les ajuster.
1
What is Kubernetes?
2
Why is it called KAS?
3
What makes it so popular?
4
Let's take a look.
5
Kubernetes is an open source container orchestration platform.
6
It automates the deployment, scaling,
7
and management of containerized applications.
8
Kubernetes can be traced back to Google's internal container orchestration system Borg,
9
which managed the deployment of thousands of applications within Google.
10
In 2014, Google open sourced a version of Borg that is Kubernetes.
11
Now, why is it called KAS?
12
This is a somewhat nerdy way of abbreviating long words.
13
The number 8 in KAS refer to the eight letters between the first letter K
14
and the last letter S in the word Kubernetes.
15
Other examples are I18N for internationalization and L10N for localization.
16
A Kubernetes cluster is a set of machines called nodes that are used to run containerized applications.
17
There are two core pieces in a Kubernetes cluster.
18
The first is the control plane.
19
It is responsible for managing the state of the cluster.
20
In production environments, the control plane usually runs on multiple nodes that span across several data center zones.
21
The second is a set of worker nodes.
22
These nodes run the containerized application workloads.
23
The containerized applications run in a pod.
24
Pods are the smallest deployable units in Kubernetes.
25
Pod hosts one or more containers and provides shared storage and networking for those containers.
26
Pods are created and managed by Kubernetes control plane.
27
They are the basic building blocks of Kubernetes applications.
28
Now let's dive a bit deeper into the control plane.
29
It consists of a number of core components.
30
They are the API server,
31
SCD, scheduler, and the controller manager.
32
The API server is the primary interface between the control plane and the rest of the cluster.
33
It exposes a RESTful API that allows clients to interact with the control plane and submit requests to manage the cluster.
34
SCD is a distributed key value store.
35
It stores the cluster's persistent state.
36
It is used by the API server and other components of the control plane to store and retrieve information about the cluster.
37
The scheduler is responsible for scheduling pods onto the worker nodes in the cluster.
38
It uses information about the resources required by the pods and the available resources on the worker nodes to make placement decisions.
39
The controller manager is responsible for running controllers that manage the state of the cluster.
40
Some examples include a replication controller,
41
which ensures that the desired number of replicas of a pod are running,
42
and the deployment controller, which manages the rolling updates and rollbacks of deployments.
43
Next, let's dive deeper into the worker nodes.
44
The core components of Kubernetes that run on the worker nodes include KubeNet,
45
Container Runtime, and KubeProxy.
46
The KubeNet is a daemon that runs on each worker node.
47
It is responsible for communicating with the control plane.
48
It receives instruction come from the control plane about
49
which pods to run on the node and ensures that the desired state of the pods is maintained.
50
The container runtime runs the containers on the worker nodes.
51
It is responsible for pulling the container images from a registry,
52
starting and stopping the containers,
53
and managing the container's resources.
54
The queue proxy is a networking proxy that runs on each worker node.
55
It is responsible for routing traffic to the correct pods.
56
It also provides load balancing for the pods and ensures that the traffic is distributed evenly across the pods.
57
So when should we use Kubernetes?
58
As with many things in software engineering,
59
this is all about trade-offs.
60
Let's look at the upsides first.
61
Kubernetes is scalable and highly available.
62
It provides features like self-healing,
63
automatic rollbacks, and horizontal scaling.
64
It makes it easy to scale our application up and down as needed,
65
allowing us to respond to changes in demand quickly.
66
Kubernetes is portable.
67
It helps us deploy and manage applications in a consistent and reliable way,
68
regardless of the underlying infrastructure.
69
It runs on premise, in a public cloud,
70
or in a hybrid environment.
71
It provides a uniform way to package, deploy, and manage applications.
72
Now, how about the downsides?
73
The number one drawback is complexity.
74
Kubernetes is complex to set up and operate.
75
The upfront cost is high,
76
especially for organizations new to container orchestration.
77
It requires a high level of expertise and resources to set up and manage a production Kubernetes environment.
78
The second drawback is cost.
79
Kubernetes requires a certain minimum level of resources to run in order to support all the features we mentioned above.
80
It's likely an overkill for many smaller organizations.
81
One popular option that strikes a reasonable balance is to offload the management of the control plane to a managed Kubernetes service.
82
Managed Kubernetes services are provided by cloud providers.
83
Some popular ones are Amazon EKS,
84
GKE on Google Cloud, and AKS on Azure.
85
These services allow organizations to run Kubernetes applications without having to worry about the underlying infrastructure.
86
They take care of tasks that require deep expertise by setting up and configuring the control plane,
87
scaling the cluster, and providing ongoing maintenance and support.
88
This is a reasonable option for a mid-sized organization to test out Kubernetes.
89
For a smaller organization, Yagni is our recommendation.
90
If you would like to learn more about system design,
91
check out our books and weekly newsletter.
92
Please subscribe if you learned something new.
93
Thank you so much, and we'll see you next time.
Télécharger l'application
Tout pour parler couramment
Prononciation IAChaque phrase notée
Phonétique (IPA)Maîtrisez chaque son
VocabulaireEnrichissez votre lexique
Jeu de vocabulaireApprenez en jouant
Même chaîne
C13
Proxy vs Reverse Proxy (Real-world Examples)
Daily ConversationUniversity StudentsWorking Adults
C12
Cache Systems Every Developer Should Know
Daily ConversationUniversity StudentsWorking Adults
C12
Top 5 Redis Use Cases
Daily ConversationUniversity Students
C13
Everything You Need to Know About DNS: Crash Course System Design #4
Daily ConversationUniversity StudentsWorking Adults
C12
CAP Theorem Simplified
Daily ConversationUniversity StudentsWorking Adults
C12
What Is REST API? Examples And How To Use It: Crash Course System Design #3
Daily ConversationUniversity StudentsWorking Adults
C18
8 Most Important System Design Concepts You Should Know
Daily ConversationUniversity StudentsWorking Adults
C11
The Secret Sauce Behind NoSQL: LSM Tree
Daily ConversationUniversity StudentsWorking Adults
C11
System Design: Why is Kafka fast?
Business EnglishUniversity StudentsWorking Adults
C16
What Are Microservices Really All About? (And When Not To Use It)
Business EnglishUniversity StudentsWorking Adults
C13
System Design Was HARD - Until You Knew the Trade-Offs
Daily ConversationUniversity StudentsWorking Adults
C13
How Does a URL Shortener Work?
Business EnglishInterview EnglishUniversity Students
C13
System Design: Why is Kafka Popular?
Business EnglishUniversity StudentsWorking Adults
C14
What is API Gateway?
Business EnglishUniversity StudentsWorking Adults
C12
10+ Key Memory & Storage Systems: Crash Course System Design #5
University StudentsWorking Adults
C24
What Is Redis Really About? Why Is It So Popular?
Business EnglishUniversity StudentsWorking Adults
C1FANG Interview Question | Process vs Thread
Daily ConversationUniversity Students
B2How Git Works: Explained in 4 Minutes
Business EnglishUniversity StudentsWorking Adults
FOR YOU
Vidéo recommandée
C11
28 phrases
Kubernetes Explained in 100 Seconds
American AccentBusiness EnglishUniversity StudentsWorking Adults
C1677 phrases
Inside PMBOK Guide 8: What Project Managers Must Know | Episode 542
Business EnglishUniversity StudentsWorking Adults
C12
51 phrases
Cloud Models - CompTIA Network+ N10-009 - 1.3
Business EnglishUniversity StudentsWorking Adults
C12
210 phrases
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C16
10 phrases
What's new in Google Cloud in less than 1 minute
Business EnglishUniversity StudentsWorking Adults
C12
239 phrases
Excellent 2 Years AWS DevOps Engineer Mock Interview with Questions and Answers | Cloud | Docker
Business EnglishInterview EnglishUniversity Students
C12
195 phrases
JavaScript Visualized - Event Loop, Web APIs, (Micro)task Queue
Business EnglishUniversity StudentsWorking Adults
C12
106 phrases
What is Engineering?: Crash Course Engineering #1
Business EnglishUniversity StudentsWorking Adults
C19
13 phrases
IOC & Dependency Injection in Spring Boot - Quick Breakdown !! #shorts
Business EnglishUniversity StudentsWorking Adults
C14
557 phrases
Kubernetes 101 - Episode 3 - Deploying Apps
Business EnglishUniversity StudentsWorking Adults
Vocabulaire et conseils d’expression pour cette leçon
Cette leçon d’expression orale de niveau C1 s’appuie sur la vidéo « Kubernetes Explained in 6 Minutes ». Les mots qui reviennent le plus souvent : Kubernetes, pod, node, plane, container. Cette vidéo contient 93 phrases et 905 mots à répéter en shadowing. La partie parlée dure 6:19. Le locuteur parle à un rythme régulier d’environ 143 mots par minute, confortable pour le shadowing. Seuls 71 % des mots font partie des 3 000 mots les plus courants en anglais, le vocabulaire est donc exigeant.
Vocabulaire clé de cette vidéo
Les 15 mots les plus avancés de la vidéo, avec leur prononciation et leur sens :
| Mot | Prononciation | Sens |
|---|---|---|
| container nom | /kənˈteɪ.nəɹ/ | récipient, contenant |
| pod nom | /ˈpɑd/ | cosse, gousse |
| cluster nom | /ˈklʌstɚ/ | groupe |
| containerize verbe | conteneuriser | |
| deployment nom | /dɪˈplɔɪmənt/ | déploiement |
| drawback nom | /ˈdɹɔˌbæk/ | inconvénient, désavantage |
| rollback nom | retrait | |
| litter nom | /ˈlɪt.ɚ/ | litière |
| proxy nom | /ˈpɹɑk.si/ | fondé de pouvoir, mandataire |
| distribute verbe | /dɪˈstɹɪbjuːt/ | distribuer |
| expertise nom | /ˌɛkspɜːˈtiːz/ | compétence, expertise |
| abbreviate verbe | /əˈbɹi.vi.eɪt/ | abréger |
| automate verbe | /ˈɔ.təˌmeɪt/ | automatiser |
| configure verbe | /kənˈfɪɡə(ɹ)/ | configurer |
| daemon nom | /ˈdiː.mən/ | démon, daemon |
Les verbes à particule que vous entendrez
| Mot | Prononciation | Sens |
|---|---|---|
| set up verbe | /ˌsɛt ˈʌp/ | mettre en place, installer |
| check out verbe | mater, regarder |
Prononciation à surveiller
- Les sons « sh » et « zh »: scheduler /ˈʃɛdjələ/, internationalization /ɪntɚˌnæʃ(ə)n(ə)ləˈzeɪʃən/, localization /ˌloʊkəlɪˈzeɪʃən/, replication /ɹɛplɪˈkeɪʃən/, recommendation /ˌɹɛkəmɛnˈdeɪʃən/
- Mots longs — placez bien l’accent: abbreviate /əˈbɹi.vi.eɪt/, internationalization /ɪntɚˌnæʃ(ə)n(ə)ləˈzeɪʃən/, localization /ˌloʊkəlɪˈzeɪʃən/, replication /ɹɛplɪˈkeɪʃən/, horizontal /ˌhoɹəˈzɑn.təl/
Les sons difficiles pour les francophones :
- /r/ anglais — langue recourbée, sans frotter la gorge: container /kənˈteɪ.nəɹ/, drawback /ˈdɹɔˌbæk/, proxy /ˈpɹɑk.si/, distribute /dɪˈstɹɪbjuːt/, abbreviate /əˈbɹi.vi.eɪt/
Comment s’entraîner avec cette vidéo
- Écoutez la vidéo en entier une fois sans parler et notez les mots que vous ne connaissez pas.
- Répétez phrase par phrase à vitesse normale, en reprenant chacune jusqu’à ce que votre rythme corresponde à celui du locuteur.
- Enregistrez-vous et comparez avec l’original, en faisant attention à des mots comme container, pod, cluster.
Qu'est-ce que la technique du Shadowing ?
Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.