Skip to Content

In Kubernetes, when configuring a Service to expose your applications, you’ll encounter three key port concepts: port, targetPort, and NodePort. Understanding the distinctions and relationships between these ports is crucial for effectively managing access to your applications running within Pods. port Definition: The port field in a Service specification defines the port on which the …

Read More about k8s – port vs targetPort vs NodePort

Minikube is a tool that simplifies the process of running Kubernetes locally, making it easier for developers to develop and test Kubernetes applications. One of the key concepts in Minikube is the use of “drivers” to set up and manage the Kubernetes cluster’s virtual environment. Understanding Minikube drivers is crucial for configuring Minikube to suit …

Read More about A Comprehensive Guide to Minikube Drivers: Which One Is Right for You?

Kubernetes, the orchestration system for managing containerized applications, offers a variety of service types to ensure your applications are accessible and communicate efficiently. Each service type caters to specific use cases, balancing accessibility with resource allocation. Let’s delve into the primary Kubernetes Service types—ClusterIP, NodePort, LoadBalancer, and cloud provider-specific LoadBalancers—to understand their use cases and …

Read More about ClusterIP NodePort LoadBalancer: Kubernetes Service Types

Pods are foundational to building and running applications in Kubernetes. They provide the execution environment for containers, encapsulating application components, managing their lifecycle, and facilitating inter-component communication and resource sharing. A Pod encapsulates one or more containers, storage resources, a unique network IP, and options that govern how the container(s) should run. Containers within a …

Read More about 2 ways to get the containers running within a specific Pod in Kubernetes

minikube start –vm-driver=none 😄 minikube v1.32.0 on Ubuntu 20.04 ✨ Using the none driver based on existing profile 👍 Starting control plane node minikube in cluster minikube 🔄 Restarting existing none bare metal machine for “minikube” … 🔗 Exiting due to NOT_FOUND_CNI_PLUGINS: 💡 Suggestion: The none driver with Kubernetes v1.24+ requires containernetworking-plugins. Exiting due to …

Read More about Minikube: Exiting due to NOT_FOUND_CNI_PLUGINS

Minikube is an invaluable tool for developers looking to test and develop Kubernetes applications locally. However, when running Minikube with Kubernetes version 1.24 or higher using the none driver and Docker as the container runtime, you might encounter the NOT_FOUND_CRI_DOCKERD error. minikube start –vm-driver=none 😄 minikube v1.32.0 on AlmaLinux 8.6 ✨ Using the none driver …

Read More about Fix: Exiting due to NOT_FOUND_CRI_DOCKERD in Minikube

minikube start –vm-driver=none 😄 minikube v1.17.1 on Ubuntu 20.04 ✨ Using the none driver based on user configuration ❌ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.20.2 requires conntrack to be installed in root’s path Understanding GUEST_MISSING_CONNTRACK error The error message you’re encountering indicates that conntrack, a required dependency for Kubernetes 1.20.2, is missing from the …

Read More about Fix: Kubernetes requires conntrack to be installed in root’s path