Why do we need another Platform Engineering community? We wanted to create a home for Platform Engineers with this in mind:
* Only quality content from the top engineers in the industry
* Vendor neutral - the solution is not in a single product
* Wholesome and inclusive - less flame wars, more collaboration and building together
* Bring end-users & operators under one big tent
* Keep it fresh & cool :)
Join us on our mission to drive platform adoption around the globe!
TBH i'm not sure why this is needed, the CLI provides everything you can ask for and it's very easy to use, GUI for helm is basically a waste of time. Am I wrong?
Validkube is an open-source site designed to help developer teams quickly validate, secure, and clean their Kubernetes YAML.
The idea behind Validkube is to fuse together the capabilities of three other popular open-source projects (kubeval, kubectl-neat and trivy) and present them in a single view, providing users with a way to ensure YAML code hygiene and security, in one place, with just a few clicks of the button.
I'd appreciate any feedback. Feel free to share your experience, and of course contribute to the project to add more capabilities and tools >>> https://github.com/komodorio/validkube
Feature flags are enabling developers to deploy with confidence, safe in the knowledge that they can always disable buggy features in production without changing the code. While this increases the speed, stability, and frequency of software updates, it’s no magic trick and still requires planning in advance and using the right tools.
The widespread adoption of Kubernetes and microservices has opened the floodgates of innovation by allowing developers to deploy continuously on epic scales and at an accelerated pace. However, moving fast often involves breaking things, and when it comes to the intricate and distributed architecture of modern K8s-based systems it’s much harder to put all the pieces back together while still moving forward.
The secret to reliable cloud-native software lies in the foundations. That’s why it is so important to invest in planning your infrastructure before you build it and to implement the right tools for prevention, mitigation, and troubleshooting.
Along with the benefits of new methodologies and technologies comes a new set of troubleshooting challenges that need to be addressed as well. In this panel discussion, we talked about the new challenges in accelerated pipelines and how to overcome them. Co-hosted with Coralogix & Komodor
I've seen many people struggle with troubleshooting Kubernetes, because they couldn't for the life of them find out what's wrong with their clusters. This happens a lot. as some events are not traced to any specific cluster or microservice, or are caused by some 3rd party integration, or are too short to notice through traditional monitoring tools (i.e Grafana). For instance, short outages of 1 second each time will not show up on your dash, but will trigger an alert. Good luck finding out why you still have an alert if all the services are healthy >< anyway it's a really cool feature that addresses a major painpoint for many on-call devs.
On April 20th 2021, we hosted a webinar, together with our friends from Epsagon, featuring our CTO & co-founder, Itiel Shwartz, and Epsagon’s tech evangelist, Chinmay Gaikwad. The event centered around the current state of Kubernetes and the microservices world, where we’re headed and how to use Epsagon and Komodor in unison to overcome the many challenges that today’s modern systems pose to developers. You can see the second half + full transcript here in the link.
This blog post gives a lot of good pointers in favor of WFH. Our startup was founded during the pandemic, and we've managed to grow, recruit and build the product, all while working remotely >>> https://komodor.com/popular/how-i-learned-to-stop-worrying-a...
Join us on our mission to drive platform adoption around the globe!