Operations | Monitoring | ITSM | DevOps | Cloud

In Part 1, we looked at some key metrics for monitoring the health and performance of your Cilium-managed Kubernetes clusters and network. In this post, we’ll look at how Hubble enables you to visualize network traffic via a CLI and user interface. But first, we’ll briefly look at Hubble’s underlying infrastructure and how it provides visibility into your environment.

Cilium is a Container Network Interface (CNI) for securing and load-balancing network traffic in your Kubernetes environment. As a CNI provider, Cilium extends the orchestrator’s existing network capabilities by giving teams more control over how they build their applications and monitor traffic. For example, vanilla Kubernetes installations typically rely on traditional firewalls and Linux-based network utilities like iptables to filter pod-to-pod traffic by an IP address or port.

Many companies like all their API calls to external services routed through Azure API Management (APIM). If you are a user of Serverless360 BAM, then one of the options is to use Azure API Management as a proxy to your BAM API and then use APIM from within Logic Apps.

Managing source code with a defined method is one vital aspect of implementing effective application development. Today, two strategies for doing this stand above the rest: trunk-based development and GitFlow. Choosing the proper method for source code control is often dependent upon several factors, such as: In this article, let’s define and compare trunk-based development and GitFlow, look at the factors that drive an organization’s decision between the two.

The DevOps practice of continuous integration and continuous deployment (CI/CD) improves software delivery. CI/CD platforms monitor and automate the application development process ensuring a better application, faster. CI/CD pipelines build code, run tests, and deploy a production-ready version of an application that has passed all automated checks.

Have you considered cloud portability, i.e., the ability to easily move workloads between on-premises systems and across multiple cloud service providers (CSPs)? The idea is that workloads should run in the environment that delivers the most value for your organization, but as that “optimal” environment can change over time, you need to be able to move your workloads accordingly.

So, you want to become a DevOps engineer? It’s a stimulating, challenging, high-paying career choice, but the lynchpin role holds software development and operations together. We’ve compiled a DevOps roadmap that includes all the steps required to fill the shoes of a DevOps expert. As you know, DevOps is a set of practices and tools to integrate and automate processes between IT and software development teams.