Operations | Monitoring | ITSM | DevOps | Cloud

We may not always know what is happening behind the scenes when we add a dependency to our projects. We expect this process to “just work” to carry on building applications. Little we may know about the level of commitment from maintainers and the amount of work needed to have everyone seamlessly use a library. Let’s hop in backstage to discover the unique way Blackfire releases its Python binaries.

When developing container-based services that will be orchestrated by Kubernetes, Terraform is an essential part of your artifact ecosystem. These infrastructure-as-code configuration files help automate the provisioning and maintenance of the cloud environments where your K8s applications will run. That’s why it’s great news that you can now store your Terraform modules, providers, and remote state files in Artifactory as a part of your software supply chain.

Having enough time available is a struggle we all experience. Technological innovations enable us to develop and deploy software at lightning speed: Sometimes we can push more to production than our organizations’ IT environments can handle. At the same time, we want to increase customer satisfaction by reducing downtime. But how are you going to keep customer satisfaction rates high if a large majority of incidents are caused by changes?

Consider what happens if digital apps or services go down. Companies lose revenue, decrease productivity, compromise customer loyalty and the list of repercussions goes on, depending on the business. Indeed, modern business continuity is contingent on a well-functioning suite of consumer and commercial apps and services.

Setting up Service Level Objectives (SLOs) is one of the foundational tasks of Site Reliability Engineering (SRE) practices, giving the SRE team a target against which to evaluate whether or not a service is running reliably enough. The inverse of your SLO is your error budget — how much unreliability you are willing to tolerate.

We consistently follow the upstream release cadence to provide our users and customers with the latest improvements and fixes, together with security maintenance and enterprise support for Kubernetes on Ubuntu. This blog is a quick overview of the latest development highlights that are made available in Canonical Kubernetes 1.24 as well as a look at our favourite upstream enhancements.

Regulatory compliance and data privacy requirements require financial institutions (FIs) to consider carefully where their applications are running and where the customer data is stored. The data protection and data sovereignty laws in most countries require an enterprise to keep data in certain geographic locations. PCI Data Security Standard, for example, regulates the way the customer and financial transactions data is stored and transmitted.

A software development life cycle (SDLC) is the sequence of steps a software project moves from conception to completion. The SDLC process specifies how to build, test, maintain, and improve specific software. Modern software development life cycles typically involve five to seven stages, depending on the model you use. Today, the SDLC comprises eight major models, from the traditional Waterfall approach to the ultra-modern Spiral Model.

With recent releases, the Kubewarden stack supports verifying the integrity and authenticity of content using the Sigstore project. In this post, we focus on Kubewarden Policies and how to create a Secure Supply Chain for them.