-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
increase maximal_ansible_version to 2.12.0 #7887
Conversation
Welcome @mmelyp! |
Hi @mmelyp. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Why not make it 2.12.0 so we don't have to constantly bump version ? |
Yes makes sense better to 2.12.0. Thank you! |
Have you tested ansible 2.11.x with kubespray? The transition to 2.10 took quite a lot of work to get running and I would pleasantly amazed if 2.11 would work out of the box. |
I personally used 2.11.3 for a while and it is fine for as far as I can tell. You can also run Kubespray with |
There's at least a problem with mitogen not supporting 2.11. |
Mitrogen has 0.3.0-RC0 with ansible 2.10+ support, so soon it will be not an issue |
yes, but 2.11 not supported and "fixes" in PR is bad. |
Well, it means, that Mitrogen has no more actual support by developer, and can't be viewed as stopping factor. |
At that rate (a year without release, no more support for new Ansible releases) I wonder if we should even keep Mitogen support in Kubespray. |
We already carry a few workarounds for mitogen without any clear benefit. It would simplify our maintenance burden to get rid of it. |
Without Mitogen, everything is very poor in terms of the speed of performing roles in Ansible, especially if there are a lot of servers. Now, if there was any alternative to it, it would be gorgeous. Or replace with something Ansible ... |
@trollqaa do you have any concrete numbers in regards to kubespray deployment speed with and without mitogen? I'm ready to nuke it from orbit since my own testing has proven for clusters with < 50 nodes to not give such a considerable advantage when applying settings like ssh pipelining (https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-pipelining) |
Another argument against mitogen: #8125 |
I just tested a scale.yml run on a 53 nodes cluster: 00:37:24 with mitogen, 00:29:31 without mitogen and with default ssh settings |
…version to avoid causing conflicts when bumping containerd_version (#8130)
* Kata-containes: Fix for ubuntu and centos sometimes kata containers fail to start because of access errors to /dev/vhost-vsock and /dev/vhost-net * Kata-containers: use similar testing strategy as gvisor * Kata-Containers: adjust values for 2.2.0 defaults Make CI tests actually pass * Kata-Containers: bump to 2.2.2 to fix sandbox_cgroup_only issue
* Ansible: separate requirements files for supported ansible versions * Ansible: allow using ansible 2.11 * CI: Exercise Ansible 2.9 and Ansible 2.11 in a basic AIO CI job * CI: Allow running a reset test outside of idempotency tests and running it in stage1 * CI: move ubuntu18-calico-aio job to stage2 and relay only on ubuntu20 with the variously supported ansible versions for stage1 * CI: add capability to install collections or roles from ansible-galaxy to mitigate missing behavior in older ansible versions
* Fixes various issues in vSphere Terraform code Provided to address various shortcomings and to fix the following issue in upstream Kubespray: #8176 * Resolves Terraform formatting issues * Sets default prefix to human-readable name * Documents new default prefix in README
Signed-off-by: EDGsheryl <edgsheryl@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mmelyp The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This can be safely closed since we implemented support for ansible 2.11 and are now validating it in CI. /close |
@cristicalin: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
No description provided.