I’ve made no secret on Reddit and other discussions of the fact that we are exploring the alternative option of adding native Docker + Compose support. K3s has been a huge disappointment in terms of bloat, stability and complexity for our purposes. It’s been the number #1 source of issues on SCALE to date. The reason people still have to speculate is because we haven’t announced if/when that might happen. Because we haven’t determined that ourselves yet… Once that is decided, nothing will be done in “secret”, just like the Netdata implementation wasn’t. This is an open source project, everything we do is visible to anybody who wants to bother spending time looking. Granted we sometimes screw up Jira visibility, but on the Github side, everything is always open..
Anyway, you really can’t get a more senior iX response than this. While we can always communicate better (and strive to do so), this will be through conversations and release notes whenever possible. We can’t sit around and argue with a brick wall all day like this thread has become. We have to get some work done in the meantime. Considering that we give this product away for free to the world, I think we’re doing a pretty decent job of trying to make forward progress, while still engaging with community feedback. The fact that we are actively looking at how to re-enable longer-term lossy stats based on that community feedback is evidence enough. If that doesn’t satisfy you, then you will have to remain unsatisfied. Meanwhile I’m going to move onto other topics that don’t beat the same dead horse over and over. 