In Soluto we use a microservices architecture, whereby each service can ship its logs to our third party logs provider and query them to create alerts and dashboards and to improve visibility. As logs multiplied, the issues started… The continuous growth of our company has presented a new challenge to our logs collection system. The weekly addition of new services to our backend architecture led to an exponential growth of our log volume. All good up to here. However, this…
At Soluto, we have super-devs who have full ownership: from writing code to deploying it to monitoring. When we made the shift to Kubernetes, we wanted to keep our devs independent and put a lot of effort into allowing them to create services rapidly. It all worked like a charm – until they had to handle credentials. This challenge leads us to build Kamus – an open source, GitOps, zero trust, secrets solution for Kubernetes applications. Kamus allows you to…
Short answer: YES (scroll to end to find out, or check out the sample repo). Long answer: Read along to find out! Kubernetes deployment seems pretty simple: all you need is just a bunch of YAML files, and by using kubectl (the Kubernetes command line utility) you’ll have your service up and running in your Kubernetes cluster. Although deploying one service is an easy task, how do you deploy hundreds of microservices? At Soluto, we have more than 100 live…
Powered by WordPress & Theme by Anders Norén