Komodor VS Signed Pages

Helm Dashboard is an open-source project by Komodor that offers a visual and user-friendly way to manage and visualize all the Helm charts installed in your clusters. Instead of using the terminal, you can leverage the Helm Dashboard's intuitive UI to perform a variety of tasks that make working with Helm a breeze. Here are some of its key features:. - Source: dev.to / 8 months ago

Speaking of tools that I think I could talk an employer into buying, how about something to help with troubleshooting Kubernetes? Komodor is an observability tool that gives you insight into what’s happening with your clusters and workloads. As distributed applications have become more complex, they’ve become more difficult to troubleshoot, and Komodor gives you an integrated view of your Kubernetes resources. Not... - Source: dev.to / almost 2 years ago

Monitoring changes in the entire Kubernetes stack requires specialized skills particularly in the effective analysis of ripple effects and context-based approach in troubleshooting problems. A K8s-native troubleshooting solution like Komodor ensures that the troubleshooting process is undertaken in an independent and efficient manner. It institutes systematization to address the chaos that is usually present when... - Source: dev.to / over 2 years ago

You can find more info on https://komodor.com or DM me (full disclosure: I work for Komodor at the moment). Source: almost 3 years ago

For Troubleshooting: Komodor Komodor is a troubleshooting tool that has been gaining popularity in the Kubernetes dev community. What Komodor offers is the ability to gain a full view of all changes across the entire k8s stack - and their ripple effects - to streamline the usually laborious task of understanding what went wrong, when something goes wrong. - Source: dev.to / almost 3 years ago

There is "Signed Pages" by the debeloper of EteSync. It is a browser extension, that checks webapps based on signatures in the html file. The addon then warns the user if the signature is not correct or - if I remember correctly - the source changed. This allows you to be sure what webapp code was delivered. But it seems like it did not really get used outside of his own projects. - Source: Hacker News / 3 months ago

EteSync has implemented something called Signed Pages, this might be worth looking closer at. This uses PGP keys which is preloaded into the browser; but I suspect that will be a barrier too high for most non-tech users. Source: 12 months ago

There are also projects like signed web pages which can also help increasing the trust level to some degree. But that requires that you can download the source code and regenerate the verification hash locally - or have other trusted methods to verify the hash value hasn't been modified as well. The current concept is reasonably sane, but it requires too much from users currently to make it widely used. Source: almost 2 years ago

> The server can at any time start serving malicious payloads True, and I call this threat model "Beware Each and Every Fetch" (BEEF) in contrast to the more common TOFU model (although if you trust a desktop app to auto-update itself then these two models might not be all that different). In any case, I think you're being a little quick to dismiss the idea of server-hosted applications. It's true that browsers... - Source: Hacker News / about 2 years ago

Something like a browser extension for this does already exist, fortunately: https://github.com/tasn/webext-signed-pages. - Source: Hacker News / about 2 years ago