Hacker News Reader

Comment by Tobani | Hacker News Reader

I like the concepts behind istio. I want to be able to use istio, but I had it running in a test/dev environment, and it would just randomly start saying 503 for my virtual services. Removing and adding the virtual service would fix it for a couple of days. I didn't have time to really spend debugging it, and I didn't see any obvious errors in the logs. :-/

View on HN

I've been monitoring istio since it was around v0.5ish and it is notorious for release regressions. Even in 1.0.x you're better off with 1.0.1 than later versions.

Istio also turned out to be way too complex for my use case, but I have found [ambassador](https://www.getambassador.io/) to fit my needs well. It is not quite the same, of course, but it covers the subset of Istio's features I need.

Yeah I'm always worried about using a product in the middle of an architecture that has 800+ open issues on GitHub.

To be fair, Kubernetes has 2137 issues open right now :)

I don't think there's any defense to this. If you look through the open issues you find stale issues, feature requests with no planned work, already resolved issues left open, "we'll get to it in a couple of releases", etc. Nobody is managing the queue.

I know it's a big corporate product, but this is a sign of bad project management, imho. At the very least they could offer to let a community member go through and clean it up if they won't do it themselves.

They have a bot which cleans up inactive stuff, marking it as stale, eventually closing issues stale with no activity. Anything worth keeping open is re-opened or a maintainer will tell the bot to un-mark it as stale.

It takes four months to close an issue with the bot. But before it closes, someone comments or removes the tag.

There are 195 issues marked stale going back two years.

It's only bad project management if you believe every issue from every rando on the Internet should be given equal attention. An open issue tracker is a poor metric for project health.

IOW, it's popular open source, the Github issue tracker is going to have a lot of noise. What would a community member do that the stale bot isn't doing? What open source project comparable to Kubernetes' scope and interest has an open tracker that exemplifies what you seek?

That's a useful thing to note. Kubernetes has a huge surface area, and you will definitely run into issues using it. That complexity is not the right choice for every org

To be fair, issue in kubernetes github are closed after 90+30d of inactivity, so even more "closed" issues were never actually resolved.

Check this, +4600 issues that were never addressed, just ignored https://github.com/kubernetes/kubernetes/issues?page=5&q=lab...

I had the exact same experience on my dev cluster. It's a bit of a scary black box if you don't have the time/experience necessary to debug it.

Reply on news.ycombinator.com