mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
Xingyu.Wang
GitHub
commit
ff7212d58d
@ -1,91 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (Morisun029)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 interview questions every Kubernetes job candidate should know)
|
||||
[#]: via: (https://opensource.com/article/19/12/kubernetes-interview-questions)
|
||||
[#]: author: (Jessica Repka https://opensource.com/users/jrepka)
|
||||
|
||||
5 interview questions every Kubernetes job candidate should know
|
||||
======
|
||||
If you're interviewing people for Kubernetes-related roles, here's what
|
||||
to ask and why it matters.
|
||||
![Pair programming][1]
|
||||
|
||||
Job interviews are hard for people on both sides of the table, but I've discovered that interviewing candidates for Kubernetes-related jobs has seemed especially hard lately. Why, you ask? For one thing, it's hard to find someone who can answer some of my questions. Also, it has been hard to confirm whether they have the right experience, regardless of their answers to my questions.
|
||||
|
||||
I'll skip over my musings on that topic and get to some questions that you should ask of any job candidate who would be working with [Kubernetes][2].
|
||||
|
||||
### What is Kubernetes?
|
||||
|
||||
I've always found this question to be one of the best ones to ask in interviews. I always hear, "I work with Kubernetes," but when I ask, "what is it?" I never get a confident answer.
|
||||
|
||||
My favorite answer is from [Chris Short][3]: "Just an API with some YAML files."
|
||||
|
||||
While he is not wrong, I'll give you a more detailed version. Kubernetes is a portable container orchestration tool that is used to automate the tasks of managing, monitoring, scaling, and deploying containerized applications.
|
||||
|
||||
I've found that "an orchestration tool for deploying containerized applications" is probably as good as you're going to get as an answer, which in my opinion is good enough. While many believe Kubernetes adds a great deal more, overall, it offers many APIs to add to this core feature: container orchestration.
|
||||
|
||||
In my opinion, this is one of the best questions you can ask in an interview, as it at least proves whether the candidate knows what Kubernetes is.
|
||||
|
||||
### What is the difference between a Kubernetes node and a pod?
|
||||
|
||||
This question reveals a great first look at the complexity of Kubernetes. It shifts the conversation to an architectural overview and can lead to many interesting follow-up details. It has also been explained incorrectly to me an innumerable amount of times.
|
||||
|
||||
A [node][4] is the worker machine. This machine can be a virtual machine (VM) or a physical machine, depending on whether you are running on a hypervisor or on bare metal. The node contains services to run containers, including the kubelet, kube-proxy, and container runtime.
|
||||
|
||||
A [pod][5] includes (1) one or more containers (2) with shared network (3) and storage (4) and the specification on how to run the containers deployed together. All four of these details are important. For bonus points, an applicant could mention that, technically, a pod is the smallest deployable unit Kubernetes can create and manage—not a container.
|
||||
|
||||
The best short answer I've received for this question is: "The node is the worker, and the pod is the thing the containers are in." The distinction matters. Most of a Kubernetes administrator's job depends on knowing when to deploy what, and nodes can be very, very expensive, depending on where they are run. I wouldn't want someone deploying nodes over and over when what they needed to do was deploy a bunch of pods.
|
||||
|
||||
### What is kubectl? (And how do you pronounce it?)
|
||||
|
||||
This question is one of my higher priority questions, but it may not be relevant for you and your team. In my organization, we don't use a graphical interface to manage our Kubernetes environments, which means command-line actions are all we do.
|
||||
|
||||
So what is [kubectl][6]? It is the command-line interface to Kubernetes. You can get and set anything from there, from gathering logs and events to editing deployments and secrets. It's always helpful to pop in a random question about how to use this tool to test the interviewee's familiarity with kubectl.
|
||||
|
||||
How do you pronounce it? Well, that's up to you (there's a big disagreement on the matter), but I will gladly point you to this great video presentation by my friend [Waldo][7].
|
||||
|
||||
### What is a namespace?
|
||||
|
||||
I haven't received an answer to this question on multiple interviews. I am not sure that namespaces are used as often in other environments as they are in the organization I work in. I'll give a short answer here: a namespace is a virtual cluster in a pod. This abstraction is what enables you to keep several virtual clusters in various environments for isolation purposes.
|
||||
|
||||
### What is a container?
|
||||
|
||||
It always helps to know what is being deployed in your pod, because what's a deployment without knowing what you're deploying in it? A container is a standard unit of software that packages up code and all its dependencies. Two optional secondary answers I have received and am OK with include: a) a slimmed-down image of an OS and b) an application running in a limited OS environment. Bonus points if you can name orchestration software that uses containers other than [Docker][8], like your favorite public cloud's container service.
|
||||
|
||||
### Other questions
|
||||
|
||||
If you're wondering why I didn't add more to this list of questions, I have an easy answer for you: these are the minimum set of things _you_ should know when you are asking candidates interview questions. The next set of questions should come from a large list of questions based on your specific team, environment, and organization. As you think through these, try to find interesting questions about how technology interacts with each other to see how people think through infrastructure challenges. Think about recent challenges your team had (outages), ask to walk through deployments step-by-step, or about strategies to improve something your team actively wants to improve (like a reduction to deployment time). The less abstract the questions, the more your asking about skills that will actually matter after the interview.
|
||||
|
||||
**[Read more: [How to prepare for a Kubernetes job interview]][9]**
|
||||
|
||||
No two environments will be the same, and this also applies when you are interviewing people. I mix up questions in every interview. I also have a small environment I can use to test interviewees. I always find that answering the questions is the easiest part, and doing the work is the real test you need to give.
|
||||
|
||||
My last bit of advice for anyone giving interviews: If you meet someone who has potential but none of the experience, give them a chance to prove themselves. I wouldn't have the knowledge and experience I have today if someone hadn't seen the potential of what I could do and given me an opportunity.
|
||||
|
||||
What are other important questions to ask interviewees about Kubernetes? Please add your list in the comments.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/kubernetes-interview-questions
|
||||
|
||||
作者：[Jessica Repka][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jrepka
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard.png?itok=kBeRTFL1 (Pair programming)
|
||||
[2]: https://kubernetes.io/
|
||||
[3]: https://twitter.com/ChrisShort
|
||||
[4]: https://kubernetes.io/docs/concepts/architecture/nodes/
|
||||
[5]: https://kubernetes.io/docs/concepts/workloads/pods/pod/
|
||||
[6]: https://kubernetes.io/docs/reference/kubectl/kubectl/
|
||||
[7]: https://opensource.com/article/18/12/kubectl-definitive-pronunciation-guide
|
||||
[8]: https://opensource.com/resources/what-docker
|
||||
[9]: https://enterprisersproject.com/article/2019/2/kubernetes-job-interview-questions-how-prepare
|
||||
@ -0,0 +1,88 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (Morisun029)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 interview questions every Kubernetes job candidate should know)
|
||||
[#]: via: (https://opensource.com/article/19/12/kubernetes-interview-questions)
|
||||
[#]: author: (Jessica Repka https://opensource.com/users/jrepka)
|
||||
|
||||
每个 Kubernetes 应聘者应该知道的5个面试题
|
||||
======
|
||||
如果你要面试Kubernetes相关的应聘者，这里给出了要提问的问题以及这些问题的重要性。
|
||||
![Pair programming][1]
|
||||
|
||||
面试对面试官及候选人来说都很不容易。最近，我发现面试 Kubernetes 相关工作的候选人似乎尤其困难。为什么呢？一方面，很难找到可以回答他们问题的人。而且，不管回答者回答的怎样，都很难确定他们是否有正确的经验。
|
||||
|
||||
跳过这个问题，让我们来看看面试[Kubernetes][2]求职者时应该提问的一些问题。
|
||||
|
||||
### Kubernetes 是什么？
|
||||
|
||||
我发现这个问题是面试中最好的问题之一。我经常听到有人说“我用Kubernetes工作”，但是当我问道“Kubernetes 是什么时，从来都没有得到过一个满意答案。
|
||||
|
||||
我最喜欢克里斯•肖特[Chris Short][3]给出的答案：“Kubernetes 就是带有一些 YAML 文件的 API 。”
|
||||
|
||||
虽然他的回答没有错，但我会给你更详细的解释。 Kubernetes 是一个便携式容器编排工具，用于自动执行管理，监控，扩展和部署容器化应用程序。
|
||||
|
||||
我认为“用于部署容器化应用程序的编排工具”这个回答可能与你期望的答案差不多了。能回答出这个，我觉得已经很不错了。尽管许多人相信 Kubernetes 可以增加很多，但总的来说，它提供了许多API来增加其核心功能：容器编排。
|
||||
|
||||
我认为，这是你在面试中可以提问的最好的问题之一，因为它至少证明了候选人是否知道 Kubernetes 是什么。
|
||||
|
||||
### Kubernetes 的 node(节点)和 Pod 有什么区别?
|
||||
|
||||
该问题揭示了候选人对 Kubernetes 复杂性的初步了解。它将对话转换为体系结构概述，并可能导向许多有趣的后续细节问题。我已经听到了无数次关于该问题的错误解释了。
|
||||
|
||||
[node][4] 是工作计算机。该计算机可以是虚拟机（VM）或物理计算机，具体取决于你是在虚拟机监控程序上运行还是在裸机上运行。该节点包含用于运行容器的服务，包括 kubelet，kube-proxy 和容器运行时。
|
||||
|
||||
[pod][5] pod 包括（1）一个或多个具有共享网络（3）和存储（4）的容器（2）以及有关如何运行一起部署的容器的规范。这四个细节都很重要。更进一步，申请人应从技术层面解释，pod 是Kubernetes 可以创建和管理的最小可部署单元，而不是容器。
|
||||
|
||||
对于这个问题，我听到的最好的简答是：“node 是计算机，而 pod 是容器中的东西。” 区别很重要。 Kubernetes 管理员的大部分工作是知道什么时间要部署什么，而节点可能非常非常昂贵，具体取决于它们的运行位置。我不希望有人一遍又一遍地部署节点，他们需要做的就是部署一堆Pod。
|
||||
|
||||
### kubectl 是什么？ （你怎么发音？）
|
||||
|
||||
这个问题是我的优先级中较高的问题之一，但可能与你和你的团队无关。在我的团队中，我们不会使用图形化界面来管理Kubernetes环境，我们使用命令行操作。
|
||||
|
||||
那么什么是[kubectl][6]？它是 Kubernetes 的命令行界面。你可以从该界面获取并设置任何内容，从收集日志和事件到编辑部署环境和机密文件。随机提问候选人关于如何使用此工具对测试候选人对 kubectl 的熟悉度是很有帮助的。
|
||||
|
||||
你是怎么读的？好吧，你随便吧（对此有很大的分歧），但是我很高兴向你介绍我朋友[Waldo][7]的精彩视频演示。
|
||||
|
||||
### 名称空间是什么？
|
||||
|
||||
在多次面试中，我都没有得到关于这个问题的答案。我不确定在其他环境中使用的名称空间是否会在我所在的团队经常使用。我在这里给出一个简短的答案：名称空间是Pod中的虚拟集群。这种抽象可以使你将多个虚拟群集保留在各种环境中以此来进行隔离。
|
||||
|
||||
### 容器是什么?
|
||||
了解 Pod 中正在部署的内容总是有帮助的，因为如果都不知道其中部署的是什么，何谈部署？容器是打包代码及其所有依赖项的软件的标准单元。我收到了两个可以接收的答案，其中包括：a）精简的操作系统映像，以及b）在受限的 OS 环境中运行的应用程序。如果你可以命名使用[Docker][8]以外的其他容器的编排软件（例如你最喜欢的公共云的容器服务），则可以得到加分。
|
||||
|
||||
### 其他问题
|
||||
如果你想知道为什么我没有在此问题列表中添加更多问题，那么我可以给出一个简单的答案：我所列出的这些问题是在面试候选人时应了解的最基本的问题。接下来的问题应该是基于具体的团队、环境及组织。如果你想知道为什么我没有在此问题列表中添加更多问题，那么我可以给出一个简单的答案：我所列出的这些问题是在面试候选人时应了解的最基本的问题。接下来的问题应该是基于具体的团队、环境及组织。
|
||||
|
||||
**[阅读更多：如何准备 Kubernetes 相关的面试？]][9]**
|
||||
|
||||
没有两个环境是完全相同的。这也适用于面试中。我在每次面试中都会混合提问。 我也有一个测试面试者的小环境。我经常发现回答问题是最容易的部分，而你所做的工作才是对你的真正的考验。
|
||||
|
||||
我给面试官的最后一点建议是：如果你遇到一个很有潜力但没有经验的候选人时，请给他们一个证明自己的机会。如果当初没有人看到我的潜力，没有给我机会的话，我不会拥有今天的知识和经验。
|
||||
|
||||
还有哪些重要的问题？请留言告诉我们。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/12/kubernetes-interview-questions
|
||||
|
||||
作者：[Jessica Repka][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[Morisun029](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jrepka
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/collab-team-pair-programming-code-keyboard.png?itok=kBeRTFL1 (Pair programming)
|
||||
[2]: https://kubernetes.io/
|
||||
[3]: https://twitter.com/ChrisShort
|
||||
[4]: https://kubernetes.io/docs/concepts/architecture/nodes/
|
||||
[5]: https://kubernetes.io/docs/concepts/workloads/pods/pod/
|
||||
[6]: https://kubernetes.io/docs/reference/kubectl/kubectl/
|
||||
[7]: https://opensource.com/article/18/12/kubectl-definitive-pronunciation-guide
|
||||
[8]: https://opensource.com/resources/what-docker
|
||||
[9]: https://enterprisersproject.com/article/2019/2/kubernetes-job-interview-questions-how-prepare
|
||||
Loading…
Reference in New Issue
Block a user