【Ansible-roles实战】02-centos7.x部署kubernetes集群

【Ansible-roles实战】02-centos7.x部署kubernetes集群

前言

本文章主要是通过ansible roles全自动化部署kubernetes v1.21.9版本集群，集群为3节点，1节点master，2节点node。主要是为了熟悉ansible-roles和ansible的模块，也可以用于部署k8s测试环境，无其他实际作用。

模块介绍

以下都是在该roles中用到的相关模块，记录一下，方便后续查询。

1. command模块

command`模块用于在远程主机上执行命令。它是Ansible的核心模块之一，可以通过SSH协议在远程主机上执行任意命令。

参数	说明
chdir	指定命令执行时的工作目录
creates	如果指定的文件或目录不存在，则执行命令
removes	如果指定的文件或目录存在，则执行命令
stdin	指定命令的标准输入
executable	指定用于执行命令的可执行文件路径
warn	设置为yes时，如果命令执行失败，将不会中止Ansible的执行。

示例

1. 存在/tmp/123.txt文件，在/tmp下执行ls -l命令，当/tmp/123.txt 不存在命令正常执行;

- name: test
  command:
    cmd: ls -l
    chdir: /tmp
    creates: /tmp/1232.txt

2. 存在/tmp/123.txt文件，在/tmp下执行ls -l命令，当/tmp/123.txt 存在命令正常执行

- name: test
  command:
    cmd: ls -l
    chdir: /tmp
    removes: /tmp/1232.txt

3. command模块将在远程主机上执行ls -l命令，并将工作目录设置为/tmp。如果/tmp/example.txt文件不存在，则执行命令。执行命令时，将使用/bin/bash可执行文件。如果/tmp/oldfile.txt文件存在，则在执行命令。如果命令执行失败，将不会中止Ansible的执行。

- name: Execute command with options
  command:
    cmd: ls -l
    chdir: /tmp
    creates: /tmp/example.txt
    executable: /bin/bash
    removes: /tmp/oldfile.txt
    warn: yes

2. lineinfile模块

Ansible的lineinfile模块是用来在文件中添加、修改或删除一行文本的模块。它可以用来自动化编辑配置文件、脚本等文本文件。

参数	说明
path	要操作的文件路径
line	要添加、修改或删除的行文本
state	行的状态，可以是present（存在）、absent（不存在）、before（在某一行之前添加）、after（在某一行之后添加）等
regexp	用来匹配行的正则表达式
backrefs	是否启用反向引用，即在regexp中使用圆括号分组，然后在line中使用\1、\2等引用这些分组。
insertafter	在哪一行之后添加新行
insertbefore	在哪一行之前添加新行
marker	用来标记插入的行的字符串，可用于后续删除操作。

示例

1. 在/etc/myfile文件中查找以# Existing line开头的行，如果找到则在该行之前添加一行文本This is a new line。如果没有找到，则不做任何操作。

- name: Add a line before a specific line
  lineinfile:
    path: /etc/myfile
    line: "This is a new line"
    state: present
    insertbefore: "# Existing line"

2. 在/etc/hosts文件中查找以127.0.0.1开头的行，如果找到则将其删除。如果没有找到，则不做任何操作。

- name: Remove localhost from /etc/hosts file
  lineinfile:
    path: /etc/hosts
    state: absent
    regexp: '^127\.0\.0\.1'

3. 在/etc/myfile文件的末尾添加一行文本This is a new line。

- name: Append a line to file
  lineinfile:
    path: /etc/myfile
    line: "This is a new line"

4. 在/etc/myfile文件中查找以# Existing line开头的行，然后在该行之前|之后添加一行文本This is a new line。

- name: Add a line before or after a line
  lineinfile:
    path: /etc/myfile
    line: "This is a new line"
    insertbefore: "# Existing line"
    
    或者
    insertafter: "# Existing line"

5. 在/etc/myfile文件中查找以Old line to be removed开头的行，然后将其删除。

- name: Remove a line from file
  lineinfile:
    path: /etc/myfile
    state: absent
    regexp: "^Old line to be removed"

6. 在/etc/myfile文件中查找以Old line to be replaced开头的行，然后将其替换为This is the new line。

- name: Replace a line in file
  lineinfile:
    path: /etc/myfile
    regexp: "^Old line to be replaced"
    line: "This is the new line"

3. sysctl模块

sysctl模块是Ansible中的一个核心模块，用于管理Linux系统的内核参数。通过该模块，可以设置或修改Linux系统内核参数，以改变系统行为或优化系统性能。(需要注意的是，sysctl模块修改的内核参数只在当前会话中生效，如果需要永久生效，需要将参数写入/etc/sysctl.conf文件中，并使用sysctl -p命令重新加载配置文件)

参数	说明
name	要设置或修改的内核参数名称，可以是单个名称或多个名称组成的列表。
value	要设置或修改的内核参数的值
state	内核参数的状态，可以是present（存在）、absent（不存在）或reset（重置为默认值）。
reload	是否重新加载内核参数配置文件。

示例

1. 将vm.swappiness参数的值设置为10。

- name: Set vm.swappiness to 10
  sysctl:
    name: vm.swappiness
    value: 10

2. 将vm.swappiness参数的值设置为10，net.ipv4.tcp_syncookies参数的值设置为1。

- name: Set multiple sysctl values
  sysctl:
    name:
      - vm.swappiness
      - net.ipv4.tcp_syncookies
    value:
      - 10
      - 1

3. 将vm.swappiness参数的值重置为默认值。

- name: Reset vm.swappiness to default value
  sysctl:
    name: vm.swappiness
    state: reset

4. 删除kernel.panic参数。

- name: Remove kernel.panic parameter
  sysctl:
    name: kernel.panic
    state: absent

5. 个任务表示要确保net.ipv4.ip_forward参数的值为1，如果该参数不存在，则创建它并设置值为1；如果该参数已经存在且值为1，则不做任何修改；如果该参数存在但值不为1，则将其修改为1。

- name: configure ip_forward
  sysctl:
    name: net.ipv4.ip_forward
    value: 1
    state: present

4. modprobe模块

modprobe模块是Ansible中的一个模块，用于管理Linux系统的内核模块。通过该模块，可以加载或卸载Linux内核模块，以改变系统行为或优化系统性能。

参数	说明
name	要加载或卸载的内核模块的名称。
state	内核模块的状态，可以是present（加载）、absent（卸载）或blacklist（将模块加入黑名单）。
blacklist	是否将模块加入黑名单。
disable	是否禁用模块。

示例

1. 加载nf_conntrack内核模块。

- name: Load a kernel module
  modprobe:
    name: nf_conntrack
    state: present

2. 卸载nf_conntrack内核模块。

- name: Unload a kernel module
  modprobe:
    name: nf_conntrack
    state: absent

3. 禁用nf_conntrack内核模块。

- name: Disable a kernel module
  modprobe:
    name: nf_conntrack
    disable: yes

4. 将nf_conntrack内核模块加入黑名单。

- name: Add a kernel module to blacklist
  modprobe:
    name: nf_conntrack
    state: blacklist

5. hostname模块

在Ansible中，可以使用hostname模块来设置主机名。该模块需要在目标主机上运行，以设置主机名。

参数	说明
name	所要设置的主机名称
state	指定主机名的状态，可选值为present（默认）和absent。如果设置为present，则将设置指定的主机名；如果设置为absent，则将删除主机名。
force	当将主机名设置为已存在的主机名时，设置为yes将强制更改主机名。默认为no
use	指定用于设置主机名的方法，默认为hostnamectl。还可以选择sysctl或/etc/hostname。

示例

1. 设置主机名为your_new_hostname，指定了使用sysctl方法来设置主机名，并且设置为强制更改主机名。

 - name: Set hostname
   hostname:
     name: your_new_hostname
     state: present
     force: yes
     use: sysctl

2. hosts指定了要设置主机名的目标主机,use默认使用hostname的方式设置

 - name: Set hostname
   hostname:
     name: your_new_hostname

关键字介绍

run_once

run_once是一个用来控制任务在整个Playbook中只运行一次的选项。这个选项可以被用于任何任务或者是模块中，以确保该任务或者模块只会在整个Playbook执行过程中的一次运行。

当在一个Playbook中有多个主机需要执行任务或模块时，如果使用run_once选项，则任务或模块仅会在第一个主机上运行，并在之后的所有主机上跳过。

语法：

- name: xxxxx
  run_once: true

示例：

1. run_once选项被设置为true，这意味着apt模块只会在整个Playbook执行过程中的第一个主机上运行，并在之后的所有主机上跳过。

- name: Install dependencies
  apt:
    name: "{{ item }}"
    state: present
  with_items:
    - package1
    - package2
  run_once: true

delegate_to

​ delegate_to是一个用于将任务或模块委托给特定主机或组的选项。这个选项可以被用于在一个主机或组上执行任务或模块，而不是在所有主机上执行。

语法：

- name: xxxxx
  delegate_to: host/host_group

示例：

1. delegate_to选项被设置为specific_host，这意味着copy模块只会在该主机上执行。这可以确保文件只会被复制到该主机上，而不会被复制到其他主机上。

- name: Copy file to a specific host
  copy:
    src: /path/to/file
    dest: /path/on/remote/host
  delegate_to: specific_host

2. delegate_to选项被设置为my_group，这意味着copy模块将在该组中的所有主机上执行。这可以确保文件会被复制到该组中的所有主机上，而不会被复制到其他主机上。

- name: Copy file to a group of hosts
  copy:
    src: /path/to/file
    dest: /path/on/remote/host
  delegate_to: my_group

local_action

​ local_action选项用于在控制节点上执行本地操作。这个选项可以被用于在控制节点上执行一些不需要在远程主机上执行的任务或模块。

语法：

- name: xxxxx
  local_action: true

示例:

1. local_action选项被设置为true，这意味着command模块将在控制节点上执行而不是在远程主机上执行

- name: Run command locally
  command: echo "Hello, world!"
  local_action: true

serial

serial选项用于控制任务或模块在多个主机之间的并发执行。这个选项可以被用于在执行任务或模块时逐个地在多个主机上执行，以避免过多的并发造成的资源瓶颈或者负载过高的情况。

示例：

1. serial选项被设置为1，这意味着apt模块将在每个主机上逐个地执行，而不是在所有主机上并发执行。

- name: Install package on all hosts one at a time
  apt:
    name: mypackage
    state: present
  serial: 1

failed_when

failed_when选项用于在特定条件下将任务或模块标记为失败。如果指定的条件满足，任务或模块将被标记为失败，但不会终止整个Playbook的执行。

示例：

1. failed_when选项被设置为disk_space.stdout_lines | last | int < 10，这意味着如果磁盘空间不足10GB，则任务将被标记为失败。但是，即使任务被标记为失败，整个Playbook的执行也不会被终止。

- name: Check disk space
  shell: df -h /
  register: disk_space
  failed_when: disk_space.stdout_lines | last | int < 10

注意：

any_errors_fatal选项可以让在任何一个任务或模块失败时立即终止整个Playbook的执行；结合failed_when选项，可以让在任务或模块执行失败时立即终止整个Playbook的执行。

Ansible_roles示例

• 目录结构

[root@master ~]# tree install_k8s/
install_k8s/
├── ansible.cfg
├── hosts
├── install.yaml
├── k8s_roles
│   ├── defaults
│   │   └── main.yml
│   ├── files
│   │   ├── daemon.json
│   │   ├── kube-flannel.yml
│   │   └── kubernetes.repo
│   ├── handlers
│   │   └── main.yml
│   ├── meta
│   │   └── main.yml
│   ├── tasks
│   │   ├── init_k8s_master.yml
│   │   ├── init_system.yml
│   │   ├── install_docker.yml
│   │   ├── install_k8s.yml
│   │   ├── join_node.yml
│   │   └── main.yml
│   ├── templates
│   │   ├── hosts.j2
│   │   ├── kubeadm-config.yml.j2
│   │   └── kube-join.yaml.j2
│   └── vars
│       └── main.yml

• hosts文件

[master]
master.example.com  ansible_host=192.168.194.128 ansible_ssh_pass=123

[node]
node1.example.com  ansible_host=192.168.194.130 ansible_ssh_pass=123
node2.example.com  ansible_host=192.168.194.131 ansible_ssh_pass=123
[root@master install_k8s]#

• ansible.cfg

# config file for ansible -- https://ansible.com/
# ===============================================

# nearly all parameters can be overridden in ansible-playbook
# or with command line flags. ansible will read ANSIBLE_CONFIG,
# ansible.cfg in the current working directory, .ansible.cfg in
# the home directory or /etc/ansible/ansible.cfg, whichever it
# finds first

[defaults]

# some basic default values...

inventory      = ./hosts
#library        = /usr/share/my_modules/
#module_utils   = /usr/share/my_module_utils/
#remote_tmp     = ~/.ansible/tmp
#local_tmp      = ~/.ansible/tmp
#plugin_filters_cfg = /etc/ansible/plugin_filters.yml
#forks          = 5
#poll_interval  = 15
#sudo_user      = root
ask_sudo_pass = False
ask_pass      = False
#transport      = smart
#remote_port    = 22
#module_lang    = C
#module_set_locale = False

# plays will gather facts by default, which contain information about
# the remote system.
#
# smart - gather by default, but don't regather if already gathered
# implicit - gather by default, turn off with gather_facts: False
# explicit - do not gather by default, must say gather_facts: True
#gathering = implicit

# This only affects the gathering done by a play's gather_facts directive,
# by default gathering retrieves all facts subsets
# all - gather all subsets
# network - gather min and network facts
# hardware - gather hardware facts (longest facts to retrieve)
# virtual - gather min and virtual facts
# facter - import facts from facter
# ohai - import facts from ohai
# You can combine them using comma (ex: network,virtual)
# You can negate them using ! (ex: !hardware,!facter,!ohai)
# A minimal set of facts is always gathered.
#gather_subset = all

# some hardware related facts are collected
# with a maximum timeout of 10 seconds. This
# option lets you increase or decrease that
# timeout to something more suitable for the
# environment.
# gather_timeout = 10

# Ansible facts are available inside the ansible_facts.* dictionary
# namespace. This setting maintains the behaviour which was the default prior
# to 2.5, duplicating these variables into the main namespace, each with a
# prefix of 'ansible_'.
# This variable is set to True by default for backwards compatibility. It
# will be changed to a default of 'False' in a future release.
# ansible_facts.
# inject_facts_as_vars = True

# additional paths to search for roles in, colon separated
roles_path    = ./k8s_roles

# uncomment this to disable SSH key host checking
host_key_checking = False

# change the default callback, you can only have one 'stdout' type  enabled at a time.
#stdout_callback = skippy


## Ansible ships with some plugins that require whitelisting,
## this is done to avoid running all of a type by default.
## These setting lists those that you want enabled for your system.
## Custom plugins should not need this unless plugin author specifies it.

# enable callback plugins, they can output to stdout but cannot be 'stdout' type.
#callback_whitelist = timer, mail

# Determine whether includes in tasks and handlers are "static" by
# default. As of 2.0, includes are dynamic by default. Setting these
# values to True will make includes behave more like they did in the
# 1.x versions.
#task_includes_static = False
#handler_includes_static = False

# Controls if a missing handler for a notification event is an error or a warning
#error_on_missing_handler = True

# change this for alternative sudo implementations
#sudo_exe = sudo

# What flags to pass to sudo
# WARNING: leaving out the defaults might create unexpected behaviours
#sudo_flags = -H -S -n

# SSH timeout
#timeout = 10

# default user to use for playbooks if user is not specified
# (/usr/bin/ansible will use current user as default)
#remote_user = root

# logging is off by default unless this path is defined
# if so defined, consider logrotate
log_path = /var/log/ansible.log

# default module name for /usr/bin/ansible
#module_name = command

# use this shell for commands executed under sudo
# you may need to change this to bin/bash in rare instances
# if sudo is constrained
#executable = /bin/sh

# if inventory variables overlap, does the higher precedence one win
# or are hash values merged together?  The default is 'replace' but
# this can also be set to 'merge'.
#hash_behaviour = replace

# by default, variables from roles will be visible in the global variable
# scope. To prevent this, the following option can be enabled, and only
# tasks and handlers within the role will see the variables there
#private_role_vars = yes

# list any Jinja2 extensions to enable here:
#jinja2_extensions = jinja2.ext.do,jinja2.ext.i18n

# if set, always use this private key file for authentication, same as
# if passing --private-key to ansible or ansible-playbook
#private_key_file = /path/to/file

# If set, configures the path to the Vault password file as an alternative to
# specifying --vault-password-file on the command line.
#vault_password_file = /path/to/vault_password_file

# format of string {{ ansible_managed }} available within Jinja2
# templates indicates to users editing templates files will be replaced.
# replacing {file}, {host} and {uid} and strftime codes with proper values.
#ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}
# {file}, {host}, {uid}, and the timestamp can all interfere with idempotence
# in some situations so the default is a static string:
#ansible_managed = Ansible managed

# by default, ansible-playbook will display "Skipping [host]" if it determines a task
# should not be run on a host.  Set this to "False" if you don't want to see these "Skipping"
# messages. NOTE: the task header will still be shown regardless of whether or not the
# task is skipped.
#display_skipped_hosts = True

# by default, if a task in a playbook does not include a name: field then
# ansible-playbook will construct a header that includes the task's action but
# not the task's args.  This is a security feature because ansible cannot know
# if the *module* considers an argument to be no_log at the time that the
# header is printed.  If your environment doesn't have a problem securing
# stdout from ansible-playbook (or you have manually specified no_log in your
# playbook on all of the tasks where you have secret information) then you can
# safely set this to True to get more informative messages.
#display_args_to_stdout = False

# by default (as of 1.3), Ansible will raise errors when attempting to dereference
# Jinja2 variables that are not set in templates or action lines. Uncomment this line
# to revert the behavior to pre-1.3.
#error_on_undefined_vars = False

# by default (as of 1.6), Ansible may display warnings based on the configuration of the
# system running ansible itself. This may include warnings about 3rd party packages or
# other conditions that should be resolved if possible.
# to disable these warnings, set the following value to False:
#system_warnings = True

# by default (as of 1.4), Ansible may display deprecation warnings for language
# features that should no longer be used and will be removed in future versions.
# to disable these warnings, set the following value to False:
#deprecation_warnings = True

# (as of 1.8), Ansible can optionally warn when usage of the shell and
# command module appear to be simplified by using a default Ansible module
# instead.  These warnings can be silenced by adjusting the following
# setting or adding warn=yes or warn=no to the end of the command line
# parameter string.  This will for example suggest using the git module
# instead of shelling out to the git command.
# command_warnings = False


# set plugin path directories here, separate with colons
#action_plugins     = /usr/share/ansible/plugins/action
#become_plugins     = /usr/share/ansible/plugins/become
#cache_plugins      = /usr/share/ansible/plugins/cache
#callback_plugins   = /usr/share/ansible/plugins/callback
#connection_plugins = /usr/share/ansible/plugins/connection
#lookup_plugins     = /usr/share/ansible/plugins/lookup
#inventory_plugins  = /usr/share/ansible/plugins/inventory
#vars_plugins       = /usr/share/ansible/plugins/vars
#filter_plugins     = /usr/share/ansible/plugins/filter
#test_plugins       = /usr/share/ansible/plugins/test
#terminal_plugins   = /usr/share/ansible/plugins/terminal
#strategy_plugins   = /usr/share/ansible/plugins/strategy


# by default, ansible will use the 'linear' strategy but you may want to try
# another one
#strategy = free

# by default callbacks are not loaded for /bin/ansible, enable this if you
# want, for example, a notification or logging callback to also apply to
# /bin/ansible runs
#bin_ansible_callbacks = False


# don't like cows?  that's unfortunate.
# set to 1 if you don't want cowsay support or export ANSIBLE_NOCOWS=1
#nocows = 1

# set which cowsay stencil you'd like to use by default. When set to 'random',
# a random stencil will be selected for each task. The selection will be filtered
# against the `cow_whitelist` option below.
#cow_selection = default
#cow_selection = random

# when using the 'random' option for cowsay, stencils will be restricted to this list.
# it should be formatted as a comma-separated list with no spaces between names.
# NOTE: line continuations here are for formatting purposes only, as the INI parser
#       in python does not support them.
#cow_whitelist=bud-frogs,bunny,cheese,daemon,default,dragon,elephant-in-snake,elephant,eyes,\
#              hellokitty,kitty,luke-koala,meow,milk,moofasa,moose,ren,sheep,small,stegosaurus,\
#              stimpy,supermilker,three-eyes,turkey,turtle,tux,udder,vader-koala,vader,www

# don't like colors either?
# set to 1 if you don't want colors, or export ANSIBLE_NOCOLOR=1
#nocolor = 1

# if set to a persistent type (not 'memory', for example 'redis') fact values
# from previous runs in Ansible will be stored.  This may be useful when
# wanting to use, for example, IP information from one group of servers
# without having to talk to them in the same playbook run to get their
# current IP information.
#fact_caching = memory

#This option tells Ansible where to cache facts. The value is plugin dependent.
#For the jsonfile plugin, it should be a path to a local directory.
#For the redis plugin, the value is a host:port:database triplet: fact_caching_connection = localhost:6379:0

#fact_caching_connection=/tmp



# retry files
# When a playbook fails a .retry file can be created that will be placed in ~/
# You can enable this feature by setting retry_files_enabled to True
# and you can change the location of the files by setting retry_files_save_path

#retry_files_enabled = False
#retry_files_save_path = ~/.ansible-retry

# squash actions
# Ansible can optimise actions that call modules with list parameters
# when looping. Instead of calling the module once per with_ item, the
# module is called once with all items at once. Currently this only works
# under limited circumstances, and only with parameters named 'name'.
#squash_actions = apk,apt,dnf,homebrew,pacman,pkgng,yum,zypper

# prevents logging of task data, off by default
#no_log = False

# prevents logging of tasks, but only on the targets, data is still logged on the master/controller
#no_target_syslog = False

# controls whether Ansible will raise an error or warning if a task has no
# choice but to create world readable temporary files to execute a module on
# the remote machine.  This option is False by default for security.  Users may
# turn this on to have behaviour more like Ansible prior to 2.1.x.  See
# https://docs.ansible.com/ansible/become.html#becoming-an-unprivileged-user
# for more secure ways to fix this than enabling this option.
#allow_world_readable_tmpfiles = False

# controls the compression level of variables sent to
# worker processes. At the default of 0, no compression
# is used. This value must be an integer from 0 to 9.
#var_compression_level = 9

# controls what compression method is used for new-style ansible modules when
# they are sent to the remote system.  The compression types depend on having
# support compiled into both the controller's python and the client's python.
# The names should match with the python Zipfile compression types:
# * ZIP_STORED (no compression. available everywhere)
# * ZIP_DEFLATED (uses zlib, the default)
# These values may be set per host via the ansible_module_compression inventory
# variable
#module_compression = 'ZIP_DEFLATED'

# This controls the cutoff point (in bytes) on --diff for files
# set to 0 for unlimited (RAM may suffer!).
#max_diff_size = 1048576

# This controls how ansible handles multiple --tags and --skip-tags arguments
# on the CLI.  If this is True then multiple arguments are merged together.  If
# it is False, then the last specified argument is used and the others are ignored.
# This option will be removed in 2.8.
#merge_multiple_cli_flags = True

# Controls showing custom stats at the end, off by default
#show_custom_stats = True

# Controls which files to ignore when using a directory as inventory with
# possibly multiple sources (both static and dynamic)
#inventory_ignore_extensions = ~, .orig, .bak, .ini, .cfg, .retry, .pyc, .pyo

# This family of modules use an alternative execution path optimized for network appliances
# only update this setting if you know how this works, otherwise it can break module execution
#network_group_modules=eos, nxos, ios, iosxr, junos, vyos

# When enabled, this option allows lookups (via variables like {{lookup('foo')}} or when used as
# a loop with `with_foo`) to return data that is not marked "unsafe". This means the data may contain
# jinja2 templating language which will be run through the templating engine.
# ENABLING THIS COULD BE A SECURITY RISK
#allow_unsafe_lookups = False

# set default errors for all plays
#any_errors_fatal = False

[inventory]
# enable inventory plugins, default: 'host_list', 'script', 'auto', 'yaml', 'ini', 'toml'
#enable_plugins = host_list, virtualbox, yaml, constructed

# ignore these extensions when parsing a directory as inventory source
#ignore_extensions = .pyc, .pyo, .swp, .bak, ~, .rpm, .md, .txt, ~, .orig, .ini, .cfg, .retry

# ignore files matching these patterns when parsing a directory as inventory source
#ignore_patterns=

# If 'true' unparsed inventory sources become fatal errors, they are warnings otherwise.
#unparsed_is_failed=False

[privilege_escalation]
#become=True
#become_method=sudo
#become_user=root
#become_ask_pass=False

[paramiko_connection]

# uncomment this line to cause the paramiko connection plugin to not record new host
# keys encountered.  Increases performance on new host additions.  Setting works independently of the
# host key checking setting above.
#record_host_keys=False

# by default, Ansible requests a pseudo-terminal for commands executed under sudo. Uncomment this
# line to disable this behaviour.
#pty=False

# paramiko will default to looking for SSH keys initially when trying to
# authenticate to remote devices.  This is a problem for some network devices
# that close the connection after a key failure.  Uncomment this line to
# disable the Paramiko look for keys function
#look_for_keys = False

# When using persistent connections with Paramiko, the connection runs in a
# background process.  If the host doesn't already have a valid SSH key, by
# default Ansible will prompt to add the host key.  This will cause connections
# running in background processes to fail.  Uncomment this line to have
# Paramiko automatically add host keys.
#host_key_auto_add = True

[ssh_connection]

# ssh arguments to use
# Leaving off ControlPersist will result in poor performance, so use
# paramiko on older platforms rather than removing it, -C controls compression use
#ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s

# The base directory for the ControlPath sockets.
# This is the "%(directory)s" in the control_path option
#
# Example:
# control_path_dir = /tmp/.ansible/cp
#control_path_dir = ~/.ansible/cp

# The path to use for the ControlPath sockets. This defaults to a hashed string of the hostname,
# port and username (empty string in the config). The hash mitigates a common problem users
# found with long hostnames and the conventional %(directory)s/ansible-ssh-%%h-%%p-%%r format.
# In those cases, a "too long for Unix domain socket" ssh error would occur.
#
# Example:
# control_path = %(directory)s/%%h-%%r
#control_path =

# Enabling pipelining reduces the number of SSH operations required to
# execute a module on the remote server. This can result in a significant
# performance improvement when enabled, however when using "sudo:" you must
# first disable 'requiretty' in /etc/sudoers
#
# By default, this option is disabled to preserve compatibility with
# sudoers configurations that have requiretty (the default on many distros).
#
#pipelining = False

# Control the mechanism for transferring files (old)
#   * smart = try sftp and then try scp [default]
#   * True = use scp only
#   * False = use sftp only
#scp_if_ssh = smart

# Control the mechanism for transferring files (new)
# If set, this will override the scp_if_ssh option
#   * sftp  = use sftp to transfer files
#   * scp   = use scp to transfer files
#   * piped = use 'dd' over SSH to transfer files
#   * smart = try sftp, scp, and piped, in that order [default]
#transfer_method = smart

# if False, sftp will not use batch mode to transfer files. This may cause some
# types of file transfer failures impossible to catch however, and should
# only be disabled if your sftp version has problems with batch mode
#sftp_batch_mode = False

# The -tt argument is passed to ssh when pipelining is not enabled because sudo 
# requires a tty by default. 
#usetty = True

# Number of times to retry an SSH connection to a host, in case of UNREACHABLE.
# For each retry attempt, there is an exponential backoff,
# so after the first attempt there is 1s wait, then 2s, 4s etc. up to 30s (max).
#retries = 3

[persistent_connection]

# Configures the persistent connection timeout value in seconds.  This value is
# how long the persistent connection will remain idle before it is destroyed.
# If the connection doesn't receive a request before the timeout value
# expires, the connection is shutdown. The default value is 30 seconds.
#connect_timeout = 30

# The command timeout value defines the amount of time to wait for a command
# or RPC call before timing out. The value for the command timeout must
# be less than the value of the persistent connection idle timeout (connect_timeout)
# The default value is 30 second.
#command_timeout = 30

[accelerate]
#accelerate_port = 5099
#accelerate_timeout = 30
#accelerate_connect_timeout = 5.0

# The daemon timeout is measured in minutes. This time is measured
# from the last activity to the accelerate daemon.
#accelerate_daemon_timeout = 30

# If set to yes, accelerate_multi_key will allow multiple
# private keys to be uploaded to it, though each user must
# have access to the system via SSH to add a new key. The default
# is "no".
#accelerate_multi_key = yes

[selinux]
# file systems that require special treatment when dealing with security context
# the default behaviour that copies the existing context or uses the user default
# needs to be changed to use the file system dependent context.
#special_context_filesystems=nfs,vboxsf,fuse,ramfs,9p,vfat

# Set this to yes to allow libvirt_lxc connections to work without SELinux.
#libvirt_lxc_noseclabel = yes

[colors]
#highlight = white
#verbose = blue
#warn = bright purple
#error = red
#debug = dark gray
#deprecate = purple
#skip = cyan
#unreachable = red
#ok = green
#changed = yellow
#diff_add = green
#diff_remove = red
#diff_lines = cyan


[diff]
# Always print diff when running ( same as always running with -D/--diff )
# always = no

# Set how many context lines to show in diff
# context = 3

• tasks/main.yml

[root@master install_k8s]# cat k8s_roles/tasks/main.yml
- name: init system info
  include_tasks:
    file: init_system.yml

- name: install docker-ce
  include_tasks:
    file: install_docker.yml

- name: install k8s
  include_tasks:
    file: install_k8s.yml

- name: init k8s_master
  include_tasks:
    file: init_k8s_master.yml
  when: inventory_hostname in groups.master

- name: join node
  include_tasks:
    file: join_node.yml
  when: inventory_hostname in groups.node
  [root@master install_k8s]#

• 完整代码

完整代码：https://github.com/xiaohaizhou/Docker-roles.git

1.  安装git和svn
	yum  -y  install   git

2. 下载整个Docker-roles项目
	git clone  https://github.com/xiaohaizhou/Docker-roles.git
	
3. 下载Docker-roles项目中的某一个roles
	svn checkout https://github.com/xiaohaizhou/Docker-roles/trunk/roles-02 
	
svn checkout <项目地址>/trunk/<文件夹路径> <本地文件夹名称>
<项目地址> 是https://github.com/xiaohaizhou/Docker-roles;
<文件夹路径> 是要下载的文件夹在项目中的路径;
<本地文件夹名称> 是要保存到本地的文件夹名称。

`