News for hackers. Stuff that matters.
Re:Polaris 1.0: Best Practices for Kubernetes Workloads by RichieMartin on Tuesday June 02, 2020 @01:18PM (#23393476)
Cool project, congratulations on the launch!

How does this project relate to other tools in the same space, such as kube-score [1] and popeye [2]?

From my point of view, the approach taken by for example kube-score where resources are matched with each other to give a better overview is extremely powerful, for example it will notice if a Service is misconfigured and wouldn't match any Pods.

1: https://github.com/zegl/kube-score

2: https://github.com/derailed/popeye.

Re:Polaris 1.0: Best Practices for Kubernetes Workloads by bbrennan on Wednesday June 03, 2020 @09:36AM (#23403171)
Popeye is a very cool project with the same general aim - it checks a lot of the same things as Polaris. It's very much CLI-first (and does an amazing job at that), while Polaris is happy to run as a CLI, a web dashboard, a validating webhook, or a CI/CD check.

kube-score I hadn't heard of, but looks very cool. You're right on matching resources - one of the requests we've gotten is to be able to check that every deployment comes with a PDB, which it looks like kube-score checks. Definitely a feature we're looking into!