Exposing Kafka from kind to a Local Windows Application

In our previous blog post, we discussed a workaround for the DNS error that occurs when an application running on a local Windows machine connects to Kafka. In this post, we will discuss the proper solution.

Our Kafka cluster runs inside Docker through a local kind Kubernetes cluster rather than directly on the host machine. Kafka advertises broker addresses using Kubernetes DNS names, which can be resolved from inside the cluster but not by an application running on Windows. To make Kafka reachable from the host, we must expose the required ports from the kind node container to the host machine.

Managing Kubernetes Clusters Efficiently with K9s Terminal UI

When working with multiple Kubernetes clusters, administrators and developers often use kubectl commands and kube config contexts to switch between clusters. While this is a powerful approach, it requires users to remember various commands and context names, which can become difficult as the number of clusters grows.

For those who prefer a more interactive way to manage Kubernetes environments, tools with user-friendly interfaces can simplify day to day operations. In this blog, we will learn about K9s, a terminal based user interface that provides an efficient way to interact with Kubernetes clusters. K9s enables users to navigate resources, monitor workloads, view logs, and manage clusters directly from the terminal.

Prerequisites: This blog is demonstrated on Windows, and Chocolatey should be installed on your machine.

Troubleshooting Kind Cluster Creation Issues

Kind (Kubernetes in Docker) is a tool used to run a lightweight Kubernetes cluster locally inside Docker containers.

It is a great platform for learning real Kubernetes behavior because clusters can be spun up easily using a single command. In this blog, we will discuss an error that occurred while creating a Kind cluster for the first time and how to resolve it.

Pre-requisites:

• Docker Desktop
• Kubectl installed
• Kind installed

Integrating Azure Key Vault with AKS via External Secrets Operator

Managing secrets centrally is a best practice in software development. Secrets should be stored and rotated in a central location, even when they are used by multiple components of an application. However, when secrets need to be accessed in different places, such as CI/CD pipelines and Kubernetes, manually copying them can lead to errors and failures caused by human mistakes.

To address this in Kubernetes, we can use External Secrets Operators, which automatically sync secrets from external secret stores such as Azure Key Vaults into Kubernetes secrets. This removes the need for manual synchronization and reduces the risk of errors due to incorrect or outdated secrets.

Pre-requites:

• Azure Kubernetes Cluster
• Azure Key vault
• Managed identity

Enhance Your Azure Kubernetes Service Experience with GitHub Copilot Plugins

This blog explains how to use GitHub Copilot Chat to perform various Azure Kubernetes Service (AKS) tasks, such as creating an AKS cluster and generating kubectl commands to interact with the cluster.

Prerequisites:

• GitHub Copilot and GitHub Copilot for Azure installed
• Azure Kubernetes Service extension for Visual Studio Code installed