-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Ansible: generalization of roles, CI, joined effort #1298
Comments
Automatic merge from submit-queue Refactor kubernetes roles Continuing effort [1] of cleaning roles for kubernetes, master and node roles. TODO: - [x] clean ``kubernetes`` role - [x] move ``download_bins.yml`` under ``node`` and ``master`` and enable installation of downloaded binaries for Fedora, CentOS and other OSes. - [x] extend the installation options with installation of distribution rpm (not just the latest) - [x] clean and refactor ``node`` role - [x] clean and refactor ``master`` role - [x] introduce ``deploy-master.yml`` and ``deploy-node.yml`` playbooks, include them in the top level playbook - [x] tag relevant tasks and introduce new scripts - [x] move CPU and Memory accounting under node role (inside ``kubelet-configuration.yml``) Some items of the TODO (new playbooks, new scripts) can be resolved only once the #967 is merged. [1] #1298
@ingvagabund Any activity on this front? I've been wondering about whether we should look at joining efforts with https://github.com/kubernetes-incubator/kubespray or perhaps with https://github.com/openshift/openshift-ansible |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Decomposition of roles to elevate modularity
As pointed by @stephenrlouie, it makes sense to generalize the roles and make them independent of playbooks [2]. To deploy kubernetes on one node cluster, there is no need for flannel. Sometimes, only kubernetes addons are needed.
Related issues:
Joined effort
Some roles are already shared via Ansible galaxy:
Others can be found for sure. It makes sense to collaborate with individual folks and elevate the effort.
CI
Run various tests on various parts of playbooks to extend the application to various linux distributions. Testing for regressions is important as well. Naming few:
Both smoke tests and unit-tests can be run over each PR. Daily digest can be taken from periodic jobs run from master HEAD.
Other effort:
Now, sooner or later it is desired to move the entire ansible code under kube-deploy repository:
Make the deployment faster:
[1] http://docs.ansible.com/ansible/galaxy.html
[2] https://github.com/openstack/openstack-ansible
The text was updated successfully, but these errors were encountered: