The latest News and Information on Containers, Kubernetes, Docker and related technologies.
Over the weekend, I visited one of my favorite grocery stores to pick up one item, my favorite fruit e.g star fruit. Because of the location, the grocery star started to implement parking validation so folks would not abuse their free parking deck for extended periods of time. As I just had a handful of star fruits, I decided to use the self-checkout. This was my first time buying produce via self-checkout.
Kubernetes, a Greek word meaning pilot, has found its way into the center stage of modern software engineering. Its in-built observability, monitoring, metrics, and self-healing make it an outstanding toolset out of the box, but its core offering has a glaring problem. The Kubernetes logging challenge is its ephemeral resources disappearing into the ether, and without some 2005-style SSHing into the correct server to find the rolled over log files, you’ll never see the log data again.
For an application developer, there is certainly a long road between an idea/feature and getting deployed into production with Kubernetes. From a development perspective, having a low barrier of entry and the ability to iterate is key. From a platform engineering/DevOps perspective, creating gains in engineering efficiency all while creating and enforcing policies that do not stifle innovation is key.
Prometheus 2.35 was released last month, focusing on a better integration with cloud providers. It also improved the service discovery, performance, and resources usage. One key change was the migration to Go v1.18. It has brought some changes in the support for TLS 1.0, 1.1, and certificates signed with the SHA1 hash function. Welcome to this first edition of What’s new in Prometheus. We love Prometheus, the de-facto open source standard monitoring tool!
