Remove the workaround DaemonSet setting fs.aio-max-nr on CI worker nodes

[rzetelskik]

The DaemonSet setting fs.aio-max-nr on our CI worker nodes, introduced as a workaround to #1231, should be removed once #749 is completed, and the DaemonSet can be replaced with NodeConfig functionality.

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[rzetelskik]

/remove-lifecycle stale
/triage accepted

[athre0z]

#749 has been marked as "not accepted". Should this issue be closed as well then? What is the general plan for dealing with aio-max-nr in K8s environment? All the issues related to automatic sysctl tuning have been closed as "not planned", but I can't find any reasoning on "why" and what the alternatives would be. Is it left to the user?

[rzetelskik]

@athre0z all of the issues created in this repository by its former owner have been closed as not planned by him on his departure from ScyllaDB's operator team. We'll be retriaging and reopening them progressively. #749 is to stay.