We could probably sum up the direction the financial services industry is headed in just two words: digital transformation. It’s the buzzy, all-encompassing focus and end goal of financial services organizations near and far, and it’s the big reason why many organizations are thinking about process automation with a greater sense of urgency.
In the world of modern Kubernetes, things have come a long way from the days of a single cluster handling one app. Now, it's common to see setups that span multiple clusters across different clouds. Initially, managing those clusters was a complicated operation with many moving parts. Using tools such as SUSE Rancher, RedHat OpenShift or AWS EKS, made managing multiple clusters somewhat easier.
Kublr team is happy to announce the new release 1.27, which we have been carefully crafting in previous months. At Kublr, we support six different versions of Kubernetes and a bunch of different clouds, so our team is focused on thoroughly testing each changed component and maintaining backward compatibility.
As engineers, we didn't want to make Signals only a replacement for what the existing incumbents do today. We've had our own gripes for years about the information architecture many old companies still force you to implement today. You should be able to send us any signal from any data source and create an alert based on some conditions. We're no strangers to building features that include conditional logic, but we upped the ante when it came to Signals.
Observability isn’t just about watching for errors or monitoring for basic health signals. Instead, it goes deeper so you can understand the “why” behind the behaviors within your system. CI/CD observability plays a key part in that. It’s about gaining an in-depth view of the entire pipeline of your continuous integration and deployment systems — looking at every code check-in, every test, every build, and every deployment.
