Can a PHP App Sail on a Kubernetes Ship? A Child’s Tale of Pods

Long ago, there was a simple PHP application called Phippy, consisting of just a single page.

Phippy lived on a host that she had to share with other scary applications, none of which she knew or wanted to interact with.

She dreamed of having her own environment—a web server she could call home, isolated from the others. Every application needs an environment; for PHP this typically includes a web server, a readable filesystem, and the PHP engine.

One day a kind whale suggested that Phippy live inside a container, which would make her happier. So Phippy migrated to a container that felt like a luxurious living room floating in the middle of the sea.

Containers give applications an isolated environment, but they often need management and connection to the outside world. Isolated containers must handle shared filesystems, network communication, scheduling, load balancing, and distribution.

The whale apologized and vanished, and just as Phippy felt despair, a captain of a massive ship appeared on the horizon. The ship, built from dozens of tied‑together rafts, looked like a giant vessel. "Hello, PHP application friend, I am Captain Kube," the wise captain said.

"Kubernetes" means captain in Greek. From the word we get "Cybernetic" and "Gubernatorial". The Kubernetes project builds a robust platform for running thousands of containers in production.

"I am Phippy," the little app said. "Nice to meet you," the captain replied, attaching a name tag to her.

Kubernetes uses labels as name tags to identify objects, allowing queries based on role, stability, or other attributes.

The captain suggested moving Phippy’s container into a cabin on the ship. Phippy happily relocated her container to a cabin on Captain Kube’s massive vessel, feeling at home.

In Kubernetes, a Pod represents a runnable unit; typically one container runs in a Pod, but tightly coupled containers can share a Pod. Kubernetes connects Pods to the network and the rest of the environment.

Phippy, fascinated by genetics and sheep, asked the captain if she could clone herself any number of times. The captain introduced her to a Replication Controller.

A Replication Controller manages any number of Pods using a Pod template that can be replicated arbitrarily, handling scaling, rolling updates, and monitoring.

After many days, Phippy lived happily with her clones, but having many copies wasn’t as perfect as expected. Captain Kube opened a tunnel between Phippy’s Replication Controller and the rest of the ship, saying that the tunnel would always remain, allowing her and other Pods to discover each other.

Services inform the rest of the Kubernetes environment (including other Pods and Replication Controllers) about the application’s endpoints; service IPs and ports stay constant as Pods come and go, enabling other applications to discover them.

Thanks to services, Phippy explored other parts of the ship and befriended Goldie. Goldie gave Phippy a gift, but Phippy had nowhere to store it. Goldie suggested putting it into a volume.

Volumes are storage locations that containers can read and write; they appear as part of the local filesystem but can be backed by local storage, Ceph, Gluster, persistent block storage, and other back‑ends.

Phippy loved life on Captain Kube’s ship, enjoying new friends, yet she longed for a bit of privacy. The captain offered her a namespace, which groups resources inside Kubernetes while providing isolation from the rest of the cluster.

Namespaces allow services, Pods, Replication Controllers, and volumes to collaborate internally while offering a degree of separation from other parts of the cluster. With her new friends, Phippy sailed the seas, had many adventures, and finally found a home.

And so Phippy lived happily ever after.