mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-13 22:30:37 +08:00
hankchow translated
This commit is contained in:
zouchong
parent
0553c050b1
commit
96f4e2851f
@ -1,266 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (HankChow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Automate your container orchestration with Ansible modules for Kubernetes)
|
||||
[#]: via: (https://opensource.com/article/20/9/ansible-modules-kubernetes)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
Automate your container orchestration with Ansible modules for Kubernetes
|
||||
======
|
||||
Combine Ansible with Kubernetes for cloud automation. Plus, get our
|
||||
cheat sheet for using the Ansible k8s module.
|
||||
![Ship captain sailing the Kubernetes seas][1]
|
||||
|
||||
[Ansible][2] is one of the best tools for automating your work. [Kubernetes][3] is one of the best tools for orchestrating containers. What happens when you combine the two? As you might expect, Ansible combined with Kubernetes lets you automate your container orchestration.
|
||||
|
||||
### Ansible modules
|
||||
|
||||
On its own, Ansible is basically just a framework for interpreting YAML files. Its true power comes from its [many modules][4]. Modules are what enable you to invoke external applications with just a few simple configuration settings in a playbook.
|
||||
|
||||
There are a few modules that deal directly with Kubernetes, and a few that handle related technology like [Docker][5] and [Podman][6]. Learning a new module is often similar to learning a new terminal command or a new API. You get familiar with a module from its documentation, you learn what arguments it accepts, and you equate its options to how you might use the application it interfaces with.
|
||||
|
||||
### Access a Kubernetes cluster
|
||||
|
||||
To try out Kubernetes modules in Ansible, you must have access to a Kubernetes cluster. If you don't have that, then you might try to open a trial account online, but most of those are short term. Instead, you can install [Minikube][7], as described on the Kubernetes website or in Bryant Son's excellent article on [getting started with Minikube][8]. Minikube provides a local instance of a single-node Kubernetes install, allowing you to configure and interact with it as you would a full cluster.
|
||||
|
||||
**[Download the [Ansible k8s cheat sheet][9]]**
|
||||
|
||||
Before installing Minikube, you must ensure that your environment is ready to serve as a virtualization backend. You may need to install `libvirt` and grant yourself permission to the `libvirt` group:
|
||||
|
||||
|
||||
```
|
||||
$ sudo dnf install libvirt
|
||||
$ sudo systemctl start libvirtd
|
||||
$ sudo usermod --append --groups libvirt `whoami`
|
||||
$ newgrp libvirt
|
||||
```
|
||||
|
||||
#### Install Python modules
|
||||
|
||||
To prepare for using Kubernetes-related Ansible modules, you should also install a few helper Python modules:
|
||||
|
||||
|
||||
```
|
||||
$ pip3.6 install kubernetes --user
|
||||
$ pip3.6 install openshift --user
|
||||
```
|
||||
|
||||
#### Start Kubernetes
|
||||
|
||||
If you're using Minikube instead of a Kubernetes cluster, use the `minikube` command to start up a local, miniaturized Kubernetes instance on your computer:
|
||||
|
||||
|
||||
```
|
||||
`$ minikube start --driver=kvm2 --kvm-network default`
|
||||
```
|
||||
|
||||
Wait for Minikube to initialize. Depending on your internet connection, this could take several minutes.
|
||||
|
||||
### Get information about your cluster
|
||||
|
||||
Once you've started your cluster successfully, you can get information about it with the `cluster-info` option:
|
||||
|
||||
|
||||
```
|
||||
$ kubectl cluster-info
|
||||
Kubernetes master is running at <https://192.168.39.190:8443>
|
||||
KubeDNS is running at <https://192.168.39.190:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy>
|
||||
|
||||
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
|
||||
```
|
||||
|
||||
### Use the k8s module
|
||||
|
||||
The entry point for using Kubernetes through Ansible is the `k8s` module, which enables you to manage Kubernetes objects from your playbooks. This module describes states resulting from `kubectl` instructions. For instance, here's how you would create a new [namespace][10] with `kubectl`:
|
||||
|
||||
|
||||
```
|
||||
`$ kubectl create namespace my-namespace`
|
||||
```
|
||||
|
||||
It's a simple action, and the YAML representation of the same result is similarly terse:
|
||||
|
||||
|
||||
```
|
||||
\- hosts: localhost
|
||||
tasks:
|
||||
- name: create namespace
|
||||
k8s:
|
||||
name: my-namespace
|
||||
api_version: v1
|
||||
kind: Namespace
|
||||
state: present
|
||||
```
|
||||
|
||||
In this case, the host is defined as `localhost`, under the assumption that you're running this against Minikube. Notice that the module in use defines the syntax of the parameters available (such as `api_version` and `kind`).
|
||||
|
||||
Before using this playbook, verify it with `yamllint`:
|
||||
|
||||
|
||||
```
|
||||
`$ yamllint example.yaml`
|
||||
```
|
||||
|
||||
Correct any errors, and then run the playbook:
|
||||
|
||||
|
||||
```
|
||||
`$ ansible-playbook ./example.yaml`
|
||||
```
|
||||
|
||||
Verify that the new namespace has been created:
|
||||
|
||||
|
||||
```
|
||||
$ kubectl get namespaces
|
||||
NAME STATUS AGE
|
||||
default Active 37h
|
||||
kube-node-lease Active 37h
|
||||
kube-public Active 37h
|
||||
kube-system Active 37h
|
||||
demo Active 11h
|
||||
my-namespace Active 3s
|
||||
```
|
||||
|
||||
### Pull a container image with Podman
|
||||
|
||||
Containers are Linux systems, almost impossibly minimal in scope, that can be managed by Kubernetes. Much of the container specifications have been defined by the [LXC project][11] and Docker. A recent addition to the container toolset is Podman, which is popular because it runs without requiring a daemon.
|
||||
|
||||
With Podman, you can pull a container image from a repository, such as Docker Hub or Quay.io. The Ansible syntax for this is simple, and all you need to know is the location of the container, which is available from the repository's website:
|
||||
|
||||
|
||||
```
|
||||
- name: pull an image
|
||||
podman_image:
|
||||
name: quay.io/jitesoft/nginx
|
||||
```
|
||||
|
||||
Verify it with `yamllint`:
|
||||
|
||||
|
||||
```
|
||||
`$ yamllint example.yaml`
|
||||
```
|
||||
|
||||
And then run the playbook:
|
||||
|
||||
|
||||
```
|
||||
$ ansible-playbook ./example.yaml
|
||||
[WARNING]: provided hosts list is empty, only localhost is available.
|
||||
Note that the implicit localhost does not match 'all'
|
||||
|
||||
PLAY [localhost] ************************
|
||||
|
||||
TASK [Gathering Facts] ************************
|
||||
ok: [localhost]
|
||||
|
||||
TASK [create k8s namespace] ************************
|
||||
ok: [localhost]
|
||||
|
||||
TASK [pull an image] ************************
|
||||
changed: [localhost]
|
||||
|
||||
PLAY RECAP ************************
|
||||
localhost: ok=3 changed=1 unreachable=0 failed=0
|
||||
skipped=0 rescued=0 ignored=0
|
||||
```
|
||||
|
||||
### Deploy with Ansible
|
||||
|
||||
You're not limited to small maintenance tasks with Ansible. Your playbook can interact with Ansible in much the same way a configuration file does with `kubectl`. In fact, in many ways, the YAML you know by using Kubernetes translates to your Ansible plays. Here's a configuration you might pass directly to `kubectl` to deploy an image (in this example, a web server):
|
||||
|
||||
|
||||
```
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: my-webserver
|
||||
spec:
|
||||
selector:
|
||||
matchLabels:
|
||||
run: my-webserver
|
||||
replicas: 1
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
run: my-webserver
|
||||
spec:
|
||||
containers:
|
||||
- name: my-webserver
|
||||
image: nginx
|
||||
ports:
|
||||
- containerPort: 80
|
||||
```
|
||||
|
||||
If you know these parameters, then you mostly know the parameters required to accomplish the same with Ansible. You can, with very little modification, move that YAML into a `definition` element in your Ansible playbook:
|
||||
|
||||
|
||||
```
|
||||
- name: deploy a web server
|
||||
k8s:
|
||||
api_version: v1
|
||||
namespace: my-namespace
|
||||
definition:
|
||||
kind: Deployment
|
||||
metadata:
|
||||
labels:
|
||||
app: nginx
|
||||
name: nginx-deploy
|
||||
spec:
|
||||
replicas: 1
|
||||
selector:
|
||||
matchLabels:
|
||||
app: nginx
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
app: nginx
|
||||
spec:
|
||||
containers:
|
||||
- name: my-webserver
|
||||
image: quay.io/jitesoft/nginx
|
||||
ports:
|
||||
- containerPort: 80
|
||||
protocol: TCP
|
||||
```
|
||||
|
||||
After running this, you can see the deployment with `kubectl`, as usual:
|
||||
|
||||
|
||||
```
|
||||
$ kubectl -n my-namespace get pods
|
||||
NAME READY STATUS
|
||||
nginx-deploy-7fdc9-t9wc2 1/1 Running
|
||||
```
|
||||
|
||||
### Modules for the cloud
|
||||
|
||||
As more development and deployments move to the cloud, it's important to understand how to automate the important aspects of your cloud. The `k8s` and `podman_image` modules are only two examples of modules related to Kubernetes and a mere fraction of modules developed for the cloud. Take a look at your workflow, find the tasks you want to track and automate, and see how Ansible can help you do more by doing less.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/9/ansible-modules-kubernetes
|
||||
|
||||
作者：[Seth Kenlon][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/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/ship_captain_devops_kubernetes_steer.png?itok=LAHfIpek (Ship captain sailing the Kubernetes seas)
|
||||
[2]: https://opensource.com/resources/what-ansible
|
||||
[3]: https://opensource.com/resources/what-is-kubernetes
|
||||
[4]: https://docs.ansible.com/ansible/latest/modules/modules_by_category.html
|
||||
[5]: https://opensource.com/resources/what-docker
|
||||
[6]: http://podman.io
|
||||
[7]: https://kubernetes.io/docs/tasks/tools/install-minikube
|
||||
[8]: https://opensource.com/article/18/10/getting-started-minikube
|
||||
[9]: https://opensource.com/downloads/ansible-k8s-cheat-sheet
|
||||
[10]: https://opensource.com/article/19/10/namespaces-and-containers-linux
|
||||
[11]: https://www.redhat.com/sysadmin/exploring-containers-lxc
|
||||
@ -0,0 +1,267 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (HankChow)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Automate your container orchestration with Ansible modules for Kubernetes)
|
||||
[#]: via: (https://opensource.com/article/20/9/ansible-modules-kubernetes)
|
||||
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
|
||||
|
||||
|
||||
使用 Ansible Kubernetes 模块实现容器编排自动化
|
||||
======
|
||||
> 在云上的 Kubernetes 中结合 Ansible 实现自动化的同时，还可以参照我们的速记表熟悉 Ansible 的 k8s 模块。
|
||||
|
||||
![Ship captain sailing the Kubernetes seas][1]
|
||||
|
||||
[Ansible][2] 是实现自动化工作的优秀工具，而 [Kubernetes][3] 则是容器编排方面的利器，要是把两者结合起来，会有怎样的效果呢？正如你所猜测的，Ansible + Kubernetes 的确可以实现容器编排自动化。
|
||||
|
||||
### Ansible 模块
|
||||
|
||||
实际上，Ansible 本身只是一个用于解释 YAML 文件的框架。它真正强大之处在于它[丰富的模块][4]，所谓<ruby>模块<rt>module</rt></ruby>，就是在 Ansible playbook 中让你得以通过简单配置就能调用外部应用程序的一些工具。
|
||||
|
||||
Ansible 中有模块可以直接操作 Kubernetes，也有对一些相关组件（例如 [Docker][5] 和 [Podman][6]）实现操作的模块。学习使用一个新模块的过程和学习新的终端命令、API 一样，可以先从文档中了解这个模块在调用的时候需要接受哪些参数，以及这些参数在外部应用程序中产生的具体作用。
|
||||
|
||||
### 访问 Kubernetes 集群
|
||||
|
||||
在使用 Ansible Kubernetes 模块之前，先要有能够访问 Kubernetes 集群的权限。在没有权限的情况下，可以尝试使用一个短期账号，但我们更推荐的是按照 Kubernetes 官网上的指引，或是参考 Braynt Son 《[入门 Kubernetes][8]》的教程安装 [Minikube][7]。Minikube 提供了一个单节点 Kubernetes 实例的安装过程，你可以像使用一个完整集群一样对其进行配置和交互。
|
||||
|
||||
**[下载 [Ansible k8s 速记表][9]]**
|
||||
|
||||
在安装 Minikube 之前，你需要确保你的环境支持虚拟化并安装 `libvirt`，然后对 `libvirt` 用户组授权：
|
||||
|
||||
|
||||
```
|
||||
$ sudo dnf install libvirt
|
||||
$ sudo systemctl start libvirtd
|
||||
$ sudo usermod --append --groups libvirt `whoami`
|
||||
$ newgrp libvirt
|
||||
```
|
||||
|
||||
#### 安装 Python 模块
|
||||
|
||||
为了能够在 Ansible 中使用 Kubernetes 相关的模块，你需要安装以下这些 Python 模块：
|
||||
|
||||
|
||||
```
|
||||
$ pip3.6 install kubernetes --user
|
||||
$ pip3.6 install openshift --user
|
||||
```
|
||||
|
||||
#### 启动 Kubernetes
|
||||
|
||||
如果你使用的是 Minikube 而不是完整的 Kubernetes 集群，请使用 `minikube` 命令在本地创建一个最精简化的 Kubernetes 实例：
|
||||
|
||||
|
||||
```
|
||||
`$ minikube start --driver=kvm2 --kvm-network default`
|
||||
```
|
||||
|
||||
然后等待 Minikube 完成初始化，这个过程所需的时间会因实际情况而异。
|
||||
|
||||
### 获取集群信息
|
||||
|
||||
集群启动以后，通过 `cluster-info` 选项就可以获取到集群相关信息了：
|
||||
|
||||
|
||||
```
|
||||
$ kubectl cluster-info
|
||||
Kubernetes master is running at <https://192.168.39.190:8443>
|
||||
KubeDNS is running at <https://192.168.39.190:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy>
|
||||
|
||||
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
|
||||
```
|
||||
|
||||
### 使用 `k8s` 模块
|
||||
|
||||
Ansible 使用 `k8s` 这个模块来实现对 Kubernetes 的操作，在 playbook 中使用 `k8s` 模块就可以对 Kuvernetes 对象进行管理。这个模块描述了 `kubectl` 命令的最终状态，例如对于以下这个使用 `kubectl` 创建新的[命名空间][10]的操作：
|
||||
|
||||
|
||||
```
|
||||
`$ kubectl create namespace my-namespace`
|
||||
```
|
||||
|
||||
这是一个很简单的操作，而对这个操作的最终状态用 YAML 文件来描述是这样的：
|
||||
|
||||
|
||||
```
|
||||
\- hosts: localhost
|
||||
tasks:
|
||||
- name: create namespace
|
||||
k8s:
|
||||
name: my-namespace
|
||||
api_version: v1
|
||||
kind: Namespace
|
||||
state: present
|
||||
```
|
||||
|
||||
如果你使用的是 Minikube，那么主机名应该定义为 `localhost`。需要注意的是，模块中对其它可用参数也定义了对应的语法（例如 `api_version` 和 `kind` 参数）。
|
||||
|
||||
在运行这个 playbook 之前，先通过 `yamllint` 命令验证是否有错误：
|
||||
|
||||
|
||||
```
|
||||
`$ yamllint example.yaml`
|
||||
```
|
||||
|
||||
确保没有错误之后，运行 playbook：
|
||||
|
||||
|
||||
```
|
||||
`$ ansible-playbook ./example.yaml`
|
||||
```
|
||||
|
||||
可以验证新的命名空间是否已经被创建出来：
|
||||
|
||||
|
||||
```
|
||||
$ kubectl get namespaces
|
||||
NAME STATUS AGE
|
||||
default Active 37h
|
||||
kube-node-lease Active 37h
|
||||
kube-public Active 37h
|
||||
kube-system Active 37h
|
||||
demo Active 11h
|
||||
my-namespace Active 3s
|
||||
```
|
||||
|
||||
### 使用 Podman 拉取容器镜像
|
||||
|
||||
容器是受 Kubernetes 管理的最小单位 Linux 系统，因此 [LXC 项目][11]和 Docker 对容器定义了很多规范。Podman 是一个最新的容器操作工具集，它不需要守护进程就可以运行，为此受到了很多用户的欢迎。
|
||||
|
||||
通过 Podman 可以从 Docker Hub 或者 Quay.io 拉取到容器镜像。这一操作对应的 Ansible 语法也很简单，只需要将存储库网站提供的镜像路径写在 playbook 中的相应位置就可以了：
|
||||
|
||||
|
||||
```
|
||||
- name: pull an image
|
||||
podman_image:
|
||||
name: quay.io/jitesoft/nginx
|
||||
```
|
||||
|
||||
使用 `yamllint` 验证：
|
||||
|
||||
|
||||
```
|
||||
`$ yamllint example.yaml`
|
||||
```
|
||||
|
||||
运行 playbook：
|
||||
|
||||
|
||||
```
|
||||
$ ansible-playbook ./example.yaml
|
||||
[WARNING]: provided hosts list is empty, only localhost is available.
|
||||
Note that the implicit localhost does not match 'all'
|
||||
|
||||
PLAY [localhost] ************************
|
||||
|
||||
TASK [Gathering Facts] ************************
|
||||
ok: [localhost]
|
||||
|
||||
TASK [create k8s namespace] ************************
|
||||
ok: [localhost]
|
||||
|
||||
TASK [pull an image] ************************
|
||||
changed: [localhost]
|
||||
|
||||
PLAY RECAP ************************
|
||||
localhost: ok=3 changed=1 unreachable=0 failed=0
|
||||
skipped=0 rescued=0 ignored=0
|
||||
```
|
||||
|
||||
### 使用 Ansible 实现部署
|
||||
|
||||
Ansible 除了可以执行小型维护任务以外，还可以通过 playbook 实现其它由 `kubectl` 实现的功能，因为两者的 YAML 文件之间只有少量的差异。 在 Kubernetes 中使用的 YAML 文件只需要稍加改动，就可以在 Ansible playbook 中使用。例如下面这个用于使用 `kubectl` 命令部署 Web 服务器的 YAML 文件：
|
||||
|
||||
|
||||
```
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: my-webserver
|
||||
spec:
|
||||
selector:
|
||||
matchLabels:
|
||||
run: my-webserver
|
||||
replicas: 1
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
run: my-webserver
|
||||
spec:
|
||||
containers:
|
||||
- name: my-webserver
|
||||
image: nginx
|
||||
ports:
|
||||
- containerPort: 80
|
||||
```
|
||||
|
||||
如果你对其中的参数比较熟悉，你只要把 YAML 文件中的大部分内容放到 playbook 中的 `definition` 部分，就可以在 Ansible 中使用了：
|
||||
|
||||
|
||||
```
|
||||
- name: deploy a web server
|
||||
k8s:
|
||||
api_version: v1
|
||||
namespace: my-namespace
|
||||
definition:
|
||||
kind: Deployment
|
||||
metadata:
|
||||
labels:
|
||||
app: nginx
|
||||
name: nginx-deploy
|
||||
spec:
|
||||
replicas: 1
|
||||
selector:
|
||||
matchLabels:
|
||||
app: nginx
|
||||
template:
|
||||
metadata:
|
||||
labels:
|
||||
app: nginx
|
||||
spec:
|
||||
containers:
|
||||
- name: my-webserver
|
||||
image: quay.io/jitesoft/nginx
|
||||
ports:
|
||||
- containerPort: 80
|
||||
protocol: TCP
|
||||
```
|
||||
|
||||
执行完成后，使用 `kubectl` 命令可以看到预期中的的<ruby>部署<rt>deployment</rt></ruby>：
|
||||
|
||||
|
||||
```
|
||||
$ kubectl -n my-namespace get pods
|
||||
NAME READY STATUS
|
||||
nginx-deploy-7fdc9-t9wc2 1/1 Running
|
||||
```
|
||||
|
||||
### 在云上使用模块
|
||||
|
||||
随着现在越来越多的开发和部署工作往云上转移的趋势，我们必须了解如何在云上实现自动化。其中 `k8s` 和 `podman_image` 这两个模块只是云开发中的其中一小部分。你可以在你的工作流程中寻找一些需要自动化的任务，并学习如何使用 Ansible 让你在这些任务上事半功倍。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/20/9/ansible-modules-kubernetes
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[HankChow](https://github.com/HankChow)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/ship_captain_devops_kubernetes_steer.png?itok=LAHfIpek (Ship captain sailing the Kubernetes seas)
|
||||
[2]: https://opensource.com/resources/what-ansible
|
||||
[3]: https://opensource.com/resources/what-is-kubernetes
|
||||
[4]: https://docs.ansible.com/ansible/latest/modules/modules_by_category.html
|
||||
[5]: https://opensource.com/resources/what-docker
|
||||
[6]: http://podman.io
|
||||
[7]: https://kubernetes.io/docs/tasks/tools/install-minikube
|
||||
[8]: https://opensource.com/article/18/10/getting-started-minikube
|
||||
[9]: https://opensource.com/downloads/ansible-k8s-cheat-sheet
|
||||
[10]: https://opensource.com/article/19/10/namespaces-and-containers-linux
|
||||
[11]: https://www.redhat.com/sysadmin/exploring-containers-lxc
|
||||
Loading…
Reference in New Issue
Block a user