Should we add mitogen support back.

[cristicalin]

With mitogen releasing https://github.com/mitogen-hq/mitogen/releases/tag/v0.3.1 I would like to probe interest from the community on reinstating full support including CI coverage.

As pointed out in #8147 (comment) I think one new minor release does not quite signal that the project is back in active development but I think the community should describe their use-cases and vote on if this feature is worth maintainer and CI time on behalf of the kubespray project.

[maxpain]

In our case, upgrade-cluster.yml on a cluster with 2 nodes without mitogen takes 1 hour 20 minutes.
With mitogen about 15 minutes.

The difference is noticeable when you have high latency between ansible host and target nodes, in my case I have latency 270ms (from Russia, Moscow to Buenos Aires, Argentina).

Another case is with a cluster in the same region where I am (latency about 5 ms): cluster.yml (installing k8s from scratch) takes about 5 minutes with mitogen and 15 minutes without.

[fungusakafungus]

In our case, mitogen makes our parallel upgrades slow: #8125

[Tristan971]

Same effects as @maxpain here with high-latency.

Some of our playbooks (incl Kubespray) are an order of magnitude faster with mitogen vs without, so it's a bit difficult to not want it to be first-class.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

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.

[Tristan971]

/reopen

While not necessarily incredibly active, the project is seeing activity, merges and fixes.

Also Ansible 6 support was just merged a week ago, which at least addresses the original main driver of its deprecation in #8147.

[k8s-ci-robot]

@Tristan971: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

While not necessarily incredibly active, the project is seeing activity, merges and fixes.

Also Ansible 6 support was just merged a week ago, which at least addresses the original main driver of its deprecation in #8147.

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.