kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kubespray/roles/kubernetes/preinstall/handlers/main.yml

99 lines
4.0 KiB
YAML
Raw Normal View History

Adding yamllinter to ci steps (#1556) * Adding yaml linter to ci check * Minor linting fixes from yamllint * Changing CI to install python pkgs from requirements.txt - adding in a secondary requirements.txt for tests - moving yamllint to tests requirements
2017-08-24 17:09:52 +08:00
---
Remove unnecessary and risky reload network for resolvconf propagation (#5322) Change-Id: I54d706f7941b4b86c4c6cd45340295577155b884
2019-11-07 02:11:52 +08:00
- name: Preinstall | propagate resolvconf to k8s components
Fix updating resolvconf Move updating resolvconf to the network restart handler to ensure changes applied to the /etc/resolv.conf. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-08-29 22:39:55 +08:00
command: /bin/true
notify:
Rework DNS stack to meet hostnet pods needs * For Debian/RedHat OS families (with NetworkManager/dhclient/resolvconf optionally enabled) prepend /etc/resolv.conf with required nameservers, options, and supersede domain and search domains via the dhclient/resolvconf hooks. * Drop (z)nodnsupdate dhclient hook and re-implement it to complement the resolvconf -u command, which is distro/cloud provider specific. Update docs as well. * Enable network restart to apply and persist changes and simplify handlers to rely on network restart only. This fixes DNS resolve for hostnet K8s pods for Red Hat OS family. Skip network restart for canal/calico plugins, unless https://github.com/projectcalico/felix/issues/1185 fixed. * Replace linefiles line plus with_items to block mode as it's faster. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com> Co-authored-by: Matthew Mosesohn <mmosesohn@mirantis.com>
2016-11-30 21:06:11 +08:00
- Preinstall | reload kubelet
When resolv.conf changes during host_resolvconf mode, we need to restart the controller to get the new file configuration. I'm not fond of this form and would like a better way, but this seems to "work".
2017-02-01 12:31:57 +08:00
- Preinstall | kube-controller configured
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
- Preinstall | kube-apiserver configured
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
- Preinstall | restart kube-controller-manager docker
- Preinstall | restart kube-controller-manager crio/containerd
- Preinstall | restart kube-apiserver docker
- Preinstall | restart kube-apiserver crio/containerd
Fix resolv.conf configuration for Fedora CoreOS. (#6138)
2020-05-18 17:27:36 +08:00
when: not ansible_os_family in ["CoreOS", "Coreos", "Container Linux by CoreOS", "Flatcar", "Flatcar Container Linux by Kinvolk"] and not is_fedora_coreos
Fix updating resolvconf Move updating resolvconf to the network restart handler to ensure changes applied to the /etc/resolv.conf. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-08-29 22:39:55 +08:00
added "Flatcar", "Flatcar Container Linux by Kinvolk" for all coreOS role (#5607)
2020-02-18 16:15:29 +08:00
- name: Preinstall | update resolvconf for Container Linux by CoreOS and Flatcar
Ensure /etc/resolv.conf content for CoreOS Use cloud-init config to replace /etc/resolv.conf with the content for kubelet to properly configure hostnet pods. Do not use systemd-resolved yet, see https://coreos.com/os/docs/latest/configuring-dns.html "Only nss-aware applications can take advantage of the systemd-resolved cache. Notably, this means that statically linked Go programs and programs running within Docker/rkt will use /etc/resolv.conf only, and will not use the systemd-resolve cache." Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-11-23 22:49:10 +08:00
command: /bin/true
notify:
Preconfigure DNS stack and docker early In order to enable offline/intranet installation cases: * Move DNS/resolvconf configuration to preinstall role. Remove skip_dnsmasq_k8s var as not needed anymore. * Preconfigure DNS stack early, which may be the case when downloading artifacts from intranet repositories. Do not configure K8s DNS resolvers for hosts /etc/resolv.conf yet early (as they may be not existing). * Reconfigure K8s DNS resolvers for hosts only after kubedns/dnsmasq was set up and before K8s apps to be created. * Move docker install task to early stage as well and unbind it from the etcd role's specific install path. Fix external flannel dependency on docker role handlers. Also fix the docker restart handlers' steps ordering to match the expected sequence (the socket then the service). * Add default resolver fact, which is the cloud provider specific and remove hardcoded GCE resolver. * Reduce default ndots for hosts /etc/resolv.conf to 2. Multiple search domains combined with high ndots values lead to poor performance of DNS stack and make ansible workers to fail very often with the "Timeout (12s) waiting for privilege escalation prompt:" error. * Update docs. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-12-07 23:57:05 +08:00
- Preinstall | apply resolvconf cloud-init
- Preinstall | reload kubelet
Use NetworkManager to manage resolv.conf in FedoraCoreOS (#6291)
2020-06-29 15:26:17 +08:00
when: ansible_os_family in ["CoreOS", "Coreos", "Container Linux by CoreOS", "Flatcar", "Flatcar Container Linux by Kinvolk"]
Allow subdomains of dns_domain and fix kubelet restarts * Add a var for ndots (default 5) and put it hosts' /etc/resolv.conf. * Poke kube dns container image to v1.7 * In order to apply changes to kubelet, notify it to be restarted on changes made to /etc/resolv.conf. Ignore errors as the kubelet may yet to be present up to the moment of the notification being processed. * Remove unnecessary kubelet restart for master role as the node role ensures it is up and running. Notify master static pods waiters for apiserver, scheduler, controller-manager instead. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-09-27 17:54:12 +08:00
Preconfigure DNS stack and docker early In order to enable offline/intranet installation cases: * Move DNS/resolvconf configuration to preinstall role. Remove skip_dnsmasq_k8s var as not needed anymore. * Preconfigure DNS stack early, which may be the case when downloading artifacts from intranet repositories. Do not configure K8s DNS resolvers for hosts /etc/resolv.conf yet early (as they may be not existing). * Reconfigure K8s DNS resolvers for hosts only after kubedns/dnsmasq was set up and before K8s apps to be created. * Move docker install task to early stage as well and unbind it from the etcd role's specific install path. Fix external flannel dependency on docker role handlers. Also fix the docker restart handlers' steps ordering to match the expected sequence (the socket then the service). * Add default resolver fact, which is the cloud provider specific and remove hardcoded GCE resolver. * Reduce default ndots for hosts /etc/resolv.conf to 2. Multiple search domains combined with high ndots values lead to poor performance of DNS stack and make ansible workers to fail very often with the "Timeout (12s) waiting for privilege escalation prompt:" error. * Update docs. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-12-07 23:57:05 +08:00
- name: Preinstall | apply resolvconf cloud-init
Ensure /etc/resolv.conf content for CoreOS Use cloud-init config to replace /etc/resolv.conf with the content for kubelet to properly configure hostnet pods. Do not use systemd-resolved yet, see https://coreos.com/os/docs/latest/configuring-dns.html "Only nss-aware applications can take advantage of the systemd-resolved cache. Notably, this means that statically linked Go programs and programs running within Docker/rkt will use /etc/resolv.conf only, and will not use the systemd-resolve cache." Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-11-23 22:49:10 +08:00
command: /usr/bin/coreos-cloudinit --from-file {{ resolveconf_cloud_init_conf }}
Use NetworkManager to manage resolv.conf in FedoraCoreOS (#6291)
2020-06-29 15:26:17 +08:00
when: ansible_os_family in ["CoreOS", "Coreos", "Container Linux by CoreOS", "Flatcar", "Flatcar Container Linux by Kinvolk"]
- name: Preinstall | update resolvconf for Fedora CoreOS
command: /bin/true
notify:
- Preinstall | reload NetworkManager
- Preinstall | reload kubelet
when: is_fedora_coreos
- name: Preinstall | reload NetworkManager
command: systemctl restart NetworkManager.service
when: is_fedora_coreos
Ensure /etc/resolv.conf content for CoreOS Use cloud-init config to replace /etc/resolv.conf with the content for kubelet to properly configure hostnet pods. Do not use systemd-resolved yet, see https://coreos.com/os/docs/latest/configuring-dns.html "Only nss-aware applications can take advantage of the systemd-resolved cache. Notably, this means that statically linked Go programs and programs running within Docker/rkt will use /etc/resolv.conf only, and will not use the systemd-resolve cache." Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-11-23 22:49:10 +08:00
Preconfigure DNS stack and docker early In order to enable offline/intranet installation cases: * Move DNS/resolvconf configuration to preinstall role. Remove skip_dnsmasq_k8s var as not needed anymore. * Preconfigure DNS stack early, which may be the case when downloading artifacts from intranet repositories. Do not configure K8s DNS resolvers for hosts /etc/resolv.conf yet early (as they may be not existing). * Reconfigure K8s DNS resolvers for hosts only after kubedns/dnsmasq was set up and before K8s apps to be created. * Move docker install task to early stage as well and unbind it from the etcd role's specific install path. Fix external flannel dependency on docker role handlers. Also fix the docker restart handlers' steps ordering to match the expected sequence (the socket then the service). * Add default resolver fact, which is the cloud provider specific and remove hardcoded GCE resolver. * Reduce default ndots for hosts /etc/resolv.conf to 2. Multiple search domains combined with high ndots values lead to poor performance of DNS stack and make ansible workers to fail very often with the "Timeout (12s) waiting for privilege escalation prompt:" error. * Update docs. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-12-07 23:57:05 +08:00
- name: Preinstall | reload kubelet
Allow subdomains of dns_domain and fix kubelet restarts * Add a var for ndots (default 5) and put it hosts' /etc/resolv.conf. * Poke kube dns container image to v1.7 * In order to apply changes to kubelet, notify it to be restarted on changes made to /etc/resolv.conf. Ignore errors as the kubelet may yet to be present up to the moment of the notification being processed. * Remove unnecessary kubelet restart for master role as the node role ensures it is up and running. Notify master static pods waiters for apiserver, scheduler, controller-manager instead. Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2016-09-27 17:54:12 +08:00
service:
name: kubelet
state: restarted
When resolv.conf changes during host_resolvconf mode, we need to restart the controller to get the new file configuration. I'm not fond of this form and would like a better way, but this seems to "work".
2017-02-01 12:31:57 +08:00
notify:
- Preinstall | kube-controller configured
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
- Preinstall | kube-apiserver configured
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
- Preinstall | restart kube-controller-manager docker
- Preinstall | restart kube-controller-manager crio/containerd
- Preinstall | restart kube-apiserver docker
- Preinstall | restart kube-apiserver crio/containerd
Restart kubelet when updating /etc/resolv.conf on all k8s nodes
2017-04-05 01:43:47 +08:00
when: not dns_early|bool
When resolv.conf changes during host_resolvconf mode, we need to restart the controller to get the new file configuration. I'm not fond of this form and would like a better way, but this seems to "work".
2017-02-01 12:31:57 +08:00
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
# FIXME(mattymo): Also restart for kubeadm mode
- name: Preinstall | kube-apiserver configured
stat: path="{{ kube_manifest_dir }}/kube-apiserver.manifest"
register: kube_apiserver_set
when: inventory_hostname in groups['kube-master'] and dns_mode != 'none' and resolvconf_mode == 'host_resolvconf'
# FIXME(mattymo): Also restart for kubeadm mode
When resolv.conf changes during host_resolvconf mode, we need to restart the controller to get the new file configuration. I'm not fond of this form and would like a better way, but this seems to "work".
2017-02-01 12:31:57 +08:00
- name: Preinstall | kube-controller configured
stat: path="{{ kube_manifest_dir }}/kube-controller-manager.manifest"
register: kube_controller_set
when: inventory_hostname in groups['kube-master'] and dns_mode != 'none' and resolvconf_mode == 'host_resolvconf'
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
- name: Preinstall | restart kube-controller-manager docker
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
shell: "docker ps -f name=k8s_POD_kube-controller-manager* -q | xargs --no-run-if-empty docker rm -f"
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
when:
- container_manager == "docker"
- inventory_hostname in groups['kube-master']
- dns_mode != 'none'
- resolvconf_mode == 'host_resolvconf'
- kube_controller_set.stat.exists
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
- name: Preinstall | restart kube-controller-manager crio/containerd
shell: crictl pods --name kube-controller-manager* -q | xargs -I% --no-run-if-empty bash -c 'crictl stopp % && crictl rmp %'
when:
- container_manager in ['crio', 'containerd']
- inventory_hostname in groups['kube-master']
- dns_mode != 'none'
- resolvconf_mode == 'host_resolvconf'
- kube_controller_set.stat.exists
- name: Preinstall | restart kube-apiserver docker
Rename default_resolver to cloud_resolver (#2209) Cloud resolvers are mandatory for hosts on GCE and OpenStack clouds. The 8.8.8.8 alternative resolver was dropped because there is already a default nameserver. The new var name reflects the purpose better. Also restart apiserver when modifying dns settings.
2018-01-31 05:26:07 +08:00
shell: "docker ps -f name=k8s_POD_kube-apiserver* -q | xargs --no-run-if-empty docker rm -f"
Add support for restart handlers for control plane on crio/containerd (#5250) * Add support for restart handlers for control plane on crio/containerd Change-Id: I8343cc4e9df7f55b732628ed01cc6e7ea5dcee85 * Update main.yml
2019-10-17 09:58:39 +08:00
when:
- container_manager == "docker"
- inventory_hostname in groups['kube-master']
- dns_mode != 'none'
- resolvconf_mode == 'host_resolvconf'
- name: Preinstall | restart kube-apiserver crio/containerd
shell: crictl pods --name kube-apiserver* -q | xargs -I% --no-run-if-empty bash -c 'crictl stopp % && crictl rmp %'
when:
- container_manager in ['crio', 'containerd']
- inventory_hostname in groups['kube-master']
- dns_mode != 'none'
- resolvconf_mode == 'host_resolvconf'
Enable systemd-resolved DNS resolution mode (#5318) Change-Id: If3e253a40782e03cde7fc4a91493517ae31fda17
2019-11-06 19:33:52 +08:00
- name: Preinstall | Restart systemd-resolved
service:
name: systemd-resolved
state: restarted