Operations | Monitoring | ITSM | DevOps | Cloud

HAProxy Technologies is proud to unveil the 2.7 release of HAProxy Data Plane API. This release was a huge undertaking, and as with the 2.6 release, we focused on extending support for configuration keywords. We are happy to announce that with this release we support all HAProxy configuration keywords in the Data Plane API. Along with enhanced keyword coverage, we’ve added the ability to specify multiple named defaults sections through the API.

Automation and it’s use of the term Runbooks can be confusing and difficult to understand, especially when first starting out. We’ve put together some frequently asked questions and answers to help beginners get started.

GitLab CI is a powerful tool for managing the software development and deployment process. It allows you to define and automate build, test, and deployment pipelines and provides features such as version control, collaboration, and continuous integration. However, while GitLab CI is an excellent tool for managing a single environment, it can have some limitations when it comes to managing multiple environments, especially dynamic environments.

In some respects, security and reliability are competing priorities. Security controls may reduce reliability, and responding to security incidents may require mission-critical systems to be paused or shut down until they're secure. The recent security incident involving CircleCI, however, shows that it's not always necessary to choose between prioritizing security or reliability.

Have you ever had to set up and/or maintain a local development environment using Docker that mirrors your production environment as much as possible? Setting-up and supporting such a docker-based local environment is no easy feat! Common problems include performance issues, broken dependencies, broken relationships between your services and uncontrolled updates of your docker images, among many other issues. So, the question is, what can we do about that?

In this blog, I explain the idea behind Distroless container images, which inspired us to create chiselled Ubuntu images — adding the “distro” back to distro-less! In a follow-up blog, I will then provide a step-by-step example of how you can create your own chiselled Ubuntu base container images, built for your specific needs.