Operations | Monitoring | ITSM | DevOps | Cloud

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. First, following a continuous delivery approach allows software development teams to release in shorter cycles, so that building, testing, and releasing can be done with greater speed and reduced error rates.

Having a proper backup recovery plan is vital to any organization's IT operation. However, when you begin to distribute workloads across data centers and regions, that process begins to become more and more complex. Container orchestration platforms such as Kubernetes have begun to ease this burden and enabled the management of distributed workloads in areas that were previously very challenging.

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. First, following a continuous delivery approach allows software development teams to release in shorter cycles, so that building, testing, and releasing can be done with greater speed and reduced error rates. As stated in an earlier post of ours, you’re doing continuous delivery when: Your software is deployable throughout its lifecycle.

In previous and great articles in here, we already talked about what Cloud is and the types that exist floating above our heads. But today, for a change, we want to focus more on one of its totally forgotten key aspects: Are clouds actually made of childish dreams and cotton candy? No! Just kidding! Today we are going to talk in “Pandora FMS discussions” about what cloud service types there are.

Continuous Integration and Continuous Delivery (CI/CD) delivers services fast, effectively, and accurately. In doing so, CI/CD pipelines have become the mainstay of effective DevOps. But this process needs accurate, timely, contextual data if it’s to operate effectively. This critical data comes in the form of logs and this article will guide you through optimizing logs for CI/CD.

As organizations build out their serverless footprint, they might find themselves managing hundreds or thousands of individual components (e.g., Amazon S3 buckets, Amazon DynamoDB tables, AWS SQS queues) for just a single application. At the same time, performance issues can crop up at any of these points, which means that having access to detailed observability data from your serverless functions is crucial for effective troubleshooting.

As cloud providers and infrastructure technologies grow their support for Windows containers, developers who use the Windows ecosystem are more and more able to enjoy the benefits of containerization. It’s quicker and easier than ever to modernize and deploy applications that use Windows-specific frameworks like .NET. Plus, Windows developers can use orchestration services like Kubernetes, Amazon ECS, or Docker Swarm to manage the complexity that containerized environments introduce.

Kubernetes has a lot of features and deployment options for running containers. One of these is the Service. In this blog post, we’ll discuss what Services are, what they can be used for, and how to create them.

The HAProxy Kubernetes Ingress Controller integrates with cert-manager to provide Let’s Encrypt TLS certificates. When it comes to TLS in Kubernetes, the first thing to appreciate when you use the HAProxy Ingress Controller is that all traffic for all services travelling to your Kubernetes cluster passes through HAProxy. Requests are then routed towards the appropriate backend services depending on metadata in the request, such as the Host header.

I’m not going to even try to pretend SysAdmin Day arrives this year under conditions anyone would call “business as usual.” I’m going to avoid the cliched and empty platitudes of “the new normal,” “unprecedented times,” and “focusing on what matters.” I’m also going to avoid needlessly reminding you how much your company, coworkers, family, and friends rely on you because of your technical knowledge and expertise.