-
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
Mitogen: deprecate the use of mitogen and remove coverage from CI #8147
Mitogen: deprecate the use of mitogen and remove coverage from CI #8147
Conversation
The reason is written well on the pull request message, thanks for doing this. /lgtm |
docs/mitogen.md
Outdated
@@ -1,5 +1,7 @@ | |||
# Mitogen | |||
|
|||
*Warning:* Mitogen support is now deprecated in kubespray due to upstream not releasing an updated version to support ansible 4.x (ansible-base 2.11.x) and above. The CI support has been stripped for mitogen and we are no longer validating any support or regressions for it. The supported playbook and documentation will be removed in a kubespray 2.19. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe don't be that specific ? The supported playbook and documentation will be removed in a future kubespray release
for example ? WDYT ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted the message to be loud and clear but yes, it's better to temper it down.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the wording, also better English language, but kept the warning note.
3552763
to
88a50a0
Compare
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks and agreed with Mitogen becoming harder to support as no real activity on their end 😢
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, floryut The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi guys, I understand that maintenance is more difficult to impossible if nothing happens on the part of upstream mitogen but I am concerned that this will slow down the execution time of Kubespray. How do you guys see this or maybe you have already tested a run without mitogen? |
@Payback159 see #7887 (comment) for some comparisons between ansible with ssh pipelining (current kubespray default) and mitogen, in our tests mitogen with modern ansible is actually slower. That said, the current deprecation does not remove the capability to use mitogen and if you source kubespray in your own playbooks you can always re-enable mitogen and submit issues and/or fixes to kubespray if you encounter issues. Secondly, I see there was a recent merge in mitogen master branch to make it work with modern ansible and should a new tag be added and released, we will happily update it in our playbooks and give up on the plan to fully drop it. To putting it back in CI, we expect mitogen upstream to have a firm commitment to maintain their project or have someone more willing to fork and maintain it. |
In our case, The difference is noticeable when you have a high latency between ansible host and target nodes, in my case I have latency 270ms (from Russia, Moscow to Buenos Aires, Argentina). |
By the way, Mitogen 0.3.1 release is here with Ansible 3, 4 and 5 support. Is it possible to roll back this MR? |
@maxpain this PR disables the CI coverage so it does not interfere with you deploying mitogen via the embedded I'm hesitant to roll this change back since a minor release is not quite proof of long term commitment. We should continue to keep an eye out for mitogen evolution and reconsider adding CI coverage back after it has proven its capability to keep up to date with changes. I think we can still merge fixes for corner cases tripped by the use of mitogen. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Mitogen upsteam is not seeing any new releases and our continued support for it hinders adoption of newer Ansible versions that would in turn give us support for newer Enterprise Linux versions like Rocky. This PR deprecates the use of mitogen in our CI and explicitly marks it as deprecated in the docs. The install playbook as well as the 3 workarounds are still left in place and I plan to remove them after we tag 2.18.
Related discussion in #7887 and #8125
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: