Skip to main content

📖 Kubernetes Glossary

LaraKube CLI speaks the language of Kubernetes, the industry-standard orchestrator for containers. While we handle the "plumbing" for you, understanding these core concepts will help you master your cluster.

For deep dives, we recommend the Official Kubernetes Documentation.

🏗 Cluster & Organization​

Cluster​

A set of node machines for running containerized applications. LaraKube CLI orchestrates your app within this cluster.

Namespace​

A virtual partition in your cluster. LaraKube CLI creates a dedicated namespace for every project (e.g., my-app-local), keeping your environments isolated.

📦 Workloads & Running Code​

Pod​

The smallest unit in Kubernetes. A Pod runs one or more containers (like your PHP app or a MySQL database). When you run larakube up, you are launching Pods.

Deployment​

Describes the "desired state" of your application. It manages the creation and scaling of Pods. If a Pod crashes, the Deployment automatically replaces it.

CronJob​

Manages time-based tasks. LaraKube CLI uses this to orchestrate the Laravel Task Scheduler.

🌍 Networking & Access​

Service​

An abstract way to expose your Pods as a network service. This is how your PHP app talks to your Database (e.g., DB_HOST=mysql).

Ingress​

The "Front Door" of your cluster. It manages external access to your services, typically HTTP. This allows you to visit your app at my-app.kube.

💾 Storage & Persistence​

PersistentVolume (PV)​

A piece of storage in the cluster that has been provisioned by an administrator or dynamically provisioned using Storage Classes.

PersistentVolumeClaim (PVC)​

A request for storage by a user. Think of it like a "Ticket" to use a piece of a PersistentVolume.

emptyDir​

A simple volume that is created when a Pod is assigned to a node and exists as long as that Pod is running. LaraKube CLI uses this for ephemeral data like temporary build tasks. It is not used for databases.

[Cluster-Native Persistence]​

LaraKube CLI's strategy of using PersistentVolumeClaims (PVCs) even in local development. This ensures that your local databases (MySQL, Postgres) keep their data even if you stop or restart your cluster.

🛠 Configuration & Customization​

ConfigMap & Secret​

Objects used to store non-confidential and sensitive data (like your .env values). LaraKube CLI automatically syncs these into your cluster.

Kustomize​

A tool for customizing Kubernetes manifests without templates. LaraKube CLI uses this to manage Base configurations and Overlays (like Local vs. Production).

Overlay​

A set of Kustomize patches that modify a base configuration for a specific environment.