Hacker News .hnnew | past | comments | ask | show | jobs | submit | manugarg's commentslogin

Thanks for sharing — I'm the author of Cloudprober. Always happy to hear thoughts or suggestions (https://github.com/cloudprober/cloudprober discussions or slack linked from the homepage - https://cloudprober.org)


https://github.com/cloudprober/cloudprober (https://cloudprober.org) fits the bill here. It is a simple yet powerful monitoring tool. You can have a minimal as well as an extensive setup with it, without the bloat or the complexity.

(Full disclosure: I'm the author)


I won't trust Harness with anything open source. It's the same company that killed the open source Drone CI after acquiring it. They changed the license such that you could contribute to it but could not use it if your revenue was more than 1 million USD. They didn't fix bugs that were well known to them because they were working on the enterprise version of it.


I went to check on this, and it seems that https://github.com/harness/drone redirects to harness/gitness. I'm now very confused.

The "Community Edition" links on https://docs.drone.io/ are all broken because of this.


Gitness is a continuation of Drone: they incorporated it in one big PR [0].

Cynically, when coupled with the CTA to star on GitHub, it feels like they did it this way to preserve the star and fork counts.

[0] https://github.com/harness/gitness/pull/3364/


Nothing cynical about that statement. We definitely want to preserve the star counts! But as the founder of Drone, and Head of Product for Gitness, I see Gitness as the next major version of Drone. Gitness is built on the Drone pipeline engine and uses significant amounts of Drone code. And in the coming months, when you upgrade to the latest version of Drone you will get Gitness. So to me, they are one and the same.


I get that you feel that they're the same, and that makes sense since you founded both projects. But what is publicly visible communicates something very different.

For example, the press release entitled "Harness Releases Gitness" is clearly describing the release of a new Harness product, not a rebranding of Drone [0]. And your README doesn't say anything like "Gitness is Drone 3.0", it says it's "powered by Drone".

You also didn't merge in a branch that built Gitness on top of Drone. Instead there's one commit that removes every single line of Drone code [1] and then another one that adds all of Gitness [2]. There's no continuity in the history between Drone and Gitness; Gitness effectively originates in one big "Initial commit" that just happens to be in the same GitHub repo as Drone used to be.

Two thirds of those stars were earned before Harness even acquired Drone [3], and it feels weird to me to see them used to push Harness's strategic move into Git hosting, even if that move is led by Drone's founder.

[0] https://www.harness.io/blog/harness-releases-gitness-open-so...

[1] https://github.com/harness/gitness/commit/7ab205375f34ab3850...

[2] https://github.com/harness/gitness/commit/e0aa6cb81ae73c0877...

[3] https://star-history.com/#harness/drone


So the only place I can find the last version of Drone is https://github.com/harness/gitness/tree/v2.20.0

You don't see how that's a bit ridiculous?

https://github.com/drone/drone redirects to harness/gitness too, leaving the entire https://github.com/drone organization without its major repo. Not to mention, again, that all GitHub links on https://www.drone.io/ are now 404.


I may be wrong but I think that DroneCI did not change its license. Before you could use it for free if your revenue was less than 1 million USD which is what is now.


They did change it, but they changed it two years before the acquisition [0].

[0] https://github.com/harness/gitness/commit/ce3855812bb00dbf19...


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: