change ansible module oc_atomic_container to atomic_container

[dudigit]

Ansible 2.4.2.0 already has atomic_container build in

diff --git a/ansible/roles/master/tasks/system_container.yml b/ansible/roles/master/tasks/system_container.yml index 274d3479..7cf7d888 100644 --- a/ansible/roles/master/tasks/system_container.yml +++ b/ansible/roles/master/tasks/system_container.yml @@ -14,19 +14,19 @@ changed_when: "'Pulling layer' in pull_result.stdout"

• name: Install or Update kubernetes-apiserver system container package

  • oc_atomic_container:
  • atomic_container: name: kube-apiserver image: "{{ kube_apiserver_system_image }}" state: latest

• name: Install or Update kubernetes-controller-manager system container package

  • oc_atomic_container:
  • atomic_container: name: kube-controller-manager image: "{{ kube_controller_manager_system_image }}" state: latest

• name: Install or Update kubernetes-scheduler system container package

  • oc_atomic_container:
  • atomic_container: name: kube-scheduler image: "{{ kube_scheduler_system_image }}" state: latest diff --git a/ansible/roles/node/tasks/system_container.yml b/ansible/roles/node/tasks/system_container.yml index 5d2b0e28..50d39598 100644 --- a/ansible/roles/node/tasks/system_container.yml +++ b/ansible/roles/node/tasks/system_container.yml @@ -9,13 +9,13 @@ changed_when: "'Pulling layer' in pull_result.stdout"

• name: Install or Update kubernetes-kubelet system container package

  • oc_atomic_container:
  • atomic_container: name: kubelet image: "{{ kubelet_system_image }}" state: latest

• name: Install or Update kubernetes-proxy system container package

  • oc_atomic_container:
  • atomic_container: name: kube-proxy image: "{{ kube_proxy_system_image }}" state: latest diff --git a/ansible/vagrant/Vagrantfile b/ansible/vagrant/Vagrantfile index 205c1a6b..87742dcc 100644 --- a/ansible/vagrant/Vagrantfile +++ b/ansible/vagrant/Vagrantfile

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten /remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close