Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Containers, Kubernetes, Docker and related technologies.

How to debug a Kubernetes application

How can you easily debug a Kubernetes application? In this episode of Kubernetes Essentials, we show how you can use the kubectl command line tool to identify and resolve bugs within your application. Watch to learn how you can use this tool to easily debug and gain greater observability over your Kubernetes application!

New Website!

We’re happy to debut our new website, highlighting our newest features! We’ve been busy updating our product UI and decided to showcase some of the work on the site. All of our case studies, whitepapers, and datasheets are now in the Resources page. We’ve also been featured on a variety of news sites, podcasts and blogs. We linked all of them in the “Speedscale in the Media” section.

Run the HAProxy Kubernetes Ingress Controller Outside of Your Kubernetes Cluster

Run your HAProxy Kubernetes Ingress Controller in External mode to reduce network hops and latency. Traditionally, you would run the HAProxy Kubernetes Ingress Controller as a pod inside your Kubernetes cluster. As a pod, it has access to other pods because they share the same pod-level network. That allows it to route and load balance traffic to applications running inside pods, but the challenge is how to connect traffic from outside the cluster to the ingress controller in the first place.

Continuously deploy custom images to an Azure container registry

The Azure container registry is Microsoft’s own hosting platform for Docker images. It is a private registry where you can store and manage private docker container images and other related artifacts. These images can then be pulled and run locally or used for container-based deployments to hosting platforms. In this tutorial, you will learn how to create a custom docker image and continuously deploy it to an Azure container registry.

Best Practices for Migrating to Helm v3 for the Enterprise

At JFrog, we rely on Kubernetes and Helm to orchestrate our systems and keep our workloads running and up-to-date. Our JFrog Cloud services had initially been deployed with Helm v2 and Tillerless plugin for enhanced security, but we have now successfully migrated our many thousands of releases to Helm v3. Like many SaaS service providers, JFrog Cloud runs with many Kubernetes clusters in different regions, across different cloud providers.

Make you Developers Happy with Rancher and Shipa

At this point, it’s fair to say that containers and Kubernetes changed the dynamics of infrastructure and platforms. It’s no secret that even though managing Kubernetes clusters is still somewhat complex, in the early days, it was even harder, which is when we saw solutions such as Rancher come up to help us address those challenges. You will inevitably run into cluster-related challenges when adopting Kubernetes.

Beyond the network: Next Generation Security and Observability with eBPF - Shaun Crampton, Tigera

Learn how eBPF will bring a richer picture of what's going on in your cluster, without changing your applications. With eBPF we can safely collect information from deep within your applications, wherever they interact with the kernel. For example, collecting detailed socket statistics to root-cause network issues, or pinpointing the precise binary inside a container that made a particular request for your audit trail. This allows for insights into the behavior (and security) of the system that previously would have needed every process to be (manually) instrumented.

How Qovery billing works

Let’s see how the Qovery billing is working as we are about launching the v2 in less than two weeks. Since we launched Qovery in January 2020, our product was free of charge for our “community” and “business” plans - even if on the pricing page it was mentioned the opposite. Making Qovery free was the perfect way to get product feedback and iterate with our users without the cost constraint.