How to deploy Laravel to Kubernetes
10 min read
Laravel is an excellent framework for developing PHP applications. Whether you need to prototype a new idea, develop an MVP (Minimum Viable Product) or release a full-fledged enterprise system, Laravel facilitates all of the development tasks and workflows.
How you deal with deploying the application is a different story. Vagrant is very good with setting up a local environment similar to a remote server. However, in production, you will most likely require more than just one web host and one database. You'll probably have separate services for several requirements. You also need to have mechanisms in place to ensure that the application is always online and that the servers can efficiently balance the load.
In this article, I’ll explain how to deal with the simple requirement of running a Laravel application as a local Kubernetes set up.
Kubernetes, Why and What?
Kubernetes is an open-source system initially designed by Google to facilitate the management of containerised applications in a clustered environment. Some refer to it as an orchestration platform, and Kubernetes is not the only available platform of this type. Although, it does have a very high and fast adoption rate. Not to mention that it is quite easy to implement once you get used to it.
If you're still wondering why someone can benefit from using Kubernetes, the answer is simple. Kubernetes makes it easier to set up and manage as many clusters as required across multiple projects.
Deploying a Laravel Application to Minikube
As I've afore-mentioned, I will be showing you how to deploy a straightforward and stateless Laravel application to Kubernetes. I aim to detail the steps involved in accomplishing this while explaining why specific actions are required. Furthermore, I will show you how to quickly scale the application and also make it available on a named host using an Ingress controller.
You can run Kubernetes on several cloud hosting providers such as Google Cloud Engine and Amazon Web Services. In this tutorial, you will run the application on Minikube, a tool that makes it easy to run Kubernetes locally.
Similar to Vagrant, Minikube is merely a Virtual Machine that contains a Kubernetes platform and Docker. You will need both to deploy your application as a Docker container and scale it to three instances using Kubernetes.
cd /to/your/working/directory git clone firstname.lastname@example.org:learnk8s/laravel-kubernetes-demo.git .
To follow with this demonstration, you will need the following installed on your local system:
Are you having problems installing and running these applications on Windows? Check out the article Getting started with Docker and Kubernetes on Windows 10, for a step by step guide.
Kubernetes deploys containerised applications, and therefore as a first step, you will need to build a Docker image of the demo application. Since this tutorial will be run locally on Minikube, you can just build a local Docker Image from the
Dockerfile included in the example code.
FROM composer:1.6.5 as build WORKDIR /app COPY . /app RUN composer install FROM php:7.1.8-apache EXPOSE 80 COPY --from=build /app /app COPY vhost.conf /etc/apache2/sites-available/000-default.conf RUN chown -R www-data:www-data /app \ && a2enmod rewrite
Dockerfile is made of two parts:
- The first part extends a PHP
composerimage so that you can install the application's dependencies.
- The second part creates a final Docker image with an Apache web server to serve the application.
Before you can test the Docker image, you will need to build it:
cd /to/your/project/directory docker build -t yourname/laravel-kubernetes-demo .
Then run the application with:
docker run -ti \ -p 8080:80 \ -e APP_KEY=base64:cUPmwHx4LXa4Z25HhzFiWCf7TlQmSqnt98pnuiHmzgY= \ laravel-kubernetes-demo
And the application should be available on
With this setup, the container is generic and the
APP_KEY is not hardcoded or shared.
Building the image within Minikube
cd /to/your/project/directory eval $(minikube docker-env) docker build -t yourname/laravel-kubernetes-demo .
Don't forget to execute the eval. Building the image within the virtual machine is necessary. You should run the command only once in the current terminal.
Deploying the image
Now that the application's image is built and available in Minikube you can go ahead with deploying it.
I always start with making sure that
kubectl is in the correct context. In this case, the context is Minikube. You can quickly switch context as follows:
kubectl config use-context minikube
then you can deploy the container image:
kubectl run laravel-kubernetes-demo \ --image=yourname/laravel-kubernetes-demo \ --port=80 \ --image-pull-policy=IfNotPresent \ --env=APP_KEY=base64:cUPmwHx4LXa4Z25HhzFiWCf7TlQmSqnt98pnuiHmzgY=
The above command tells
kubectl to run our demo application from the Docker image. The first parameter of the command simply asks
kubectl to not pull the image from a registry such as Docker Hub if it exists locally which in this case it does. Do note that you still need to be logged on to Docker's so that
kubectl can check if the image is up to date.
You can check that a Pod is created for the application by running:
kubectl get pods
which should return a similar output to:
NAME READY STATUS RESTARTS AGE laravel-kubernetes-demo-7dbb9d6b48-q54wp 1/1 Running 0 18m
You can also use the Minikube GUI dashboard to monitor the cluster. The GUI also helps with visualising most of the discussed concepts. To view the dashboard, just run the following:
or to acquire the dashboard's URL address:
minikube dashboard --url=true
Exposing a Service
So far you have created a deployment which is running the application's container. A Pod running in the cluster has a dynamic IP. If you route the traffic directly to it using the IP, you may still need to update the routing table every time you restart the Pod. In fact, on every deployment or container restart, a new IP is assigned to the Pod. To avoid managing IP addresses manually, you need to use a Service. The Service acts as a load balancer for a set of Pods. So even if the IP address of a Pod changes, the service is always pointing to it. And since the Service always has the same IP, you won't need to update anything manually.
You can create a service with:
kubectl expose deployment laravel-kubernetes-demo --type=NodePort --port=80
and provided all went well, you will see a confirmation similar to:
service "laravel-kubernetes-demo" exposed
Running the following command:
kubectl get services
will show you a list of running services. You can also view the running service under the "Services" navigation menu within the dashboard. A more exciting way to verify this deployment and the service exposure is obviously seeing the running application in the browser 😊
To obtain the URL of the application (service), you can use the following command:
minikube service --url=true laravel-kubernetes-demo
which will output the IP address and port number similar to:
or, launch the application directly in the browser:
minikube service laravel-kubernetes-demo
Are you enjoying reading this article?
Subscribe to receive email notifications when I publish new articles and code libraries.
I will not share your email address with anyone, and you can unsubscribe at any time.
And that is it. You have successfully deployed the application in Kubernetes. It's exciting. But what's the point of doing all of this? Well, you only have one deployment with a single Pod running, provisioned to a Node with the exposed web service. Let's scale this deployment to two more instances of the application.
So that you understand where you are at this moment, run the following command to get a list of desired and available Pods:
kubectl get deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE laravel-kubernetes-demo 1 1 1 1 57m
The output will be "1" for each. You want to have three available Pods so let's scale this up:
kubectl scale --replicas=3 deployment/laravel-kubernetes-demo deployment "laravel-kubernetes-demo" scaled
Done. You have replicated the first Pod to another two, giving you three Pods running this service. Running the
get deployment command will verify this.
kubectl get deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE laravel-kubernetes-demo 3 3 3 3 59m
You can also see this in the Dashboard under Pods or in the Service detail screen.
Now you're running three instances of the applications using three Pods.
Imagine your application becoming even more popular. Thousands of visitors are using your website or software. In the past, you may have been busy writing more scripts to create more instances of your application. In Kubernetes you can scale to multiple instances in a snap:
kubectl scale --replicas=10 deployment/laravel-kubernetes-demo deployment "laravel-kubernetes-demo" scaled
You can see how convenient it is to use Kubernetes to scale your website.
You've already achieved great things, you deployed the application and scaled the deployment. You have already seen the running application in the browser when pointed to the cluster's (Minikube) IP address and node's port number. Now, you will see how to access the application through an assigned URL as you would do when deploying to the cloud.
To use a URL in Kubernetes, you need an Ingress. An Ingress is a set of rules to allow inbound connections to reach a Kubernetes cluster. The Ingress is necessary because, in Kubernetes, resources such as Pods only have IP addresses which are routable by and within the cluster. Meaning that they are not accessible or reachable to and from the world outside.
I have included an
ingress.yaml file with the source code of this demo application with the following contents:
apiVersion: extensions/v1beta1 kind: Ingress metadata: name: laravel-kubernetes-demo-ingress annotations: ingress.kubernetes.io/rewrite-target: / spec: backend: serviceName: default-http-server servicePort: 80 rules: - host: laravel-kubernetes.demo - http: paths: - path: / backend: serviceName: laravel-kubernetes-demo servicePort: 80
Among the basic content you would expect from a Kubernetes resource file, this file defines a set of rules to follow when routing inbound traffic. The
laravel-kubernetes.demo URL will point to the Service where the application is running, as previously labelled
laravel-kubernetes-demo on port 8181.
The Ingress resource is useless without an Ingress controller so you will need to create a new controller or use an existing one. This tutorial uses the Nginx Ingress controller for routing the traffic. Minikube (v0.14 and above) comes with the Nginx setup as an addon which you will need to enable manually:
minikube addons enable ingress
Please note that it may take few minutes for Minikube to download and install Nginx as an Ingress.
Once you have enabled the Ingress addon, you can create the Ingress in this way:
kubectl create -f path-to-your-ingress-file.yaml
You can verify and obtain the Ingress' information by running the following command:
kubectl describe ing laravel-kubernetes-demo-ingress
which outputs something similar to:
Name: laravel-kubernetes-demo-ingress Namespace: default Address: 192.168.99.101 Default backend: default-http-server:80 (<none>) Rules: Host Path Backends ---- ---- -------- * / laravel-kubernetes-demo:8181 (172.17.0.6:8181) Annotations: rewrite-target: / Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal CREATE 39s nginx-ingress-controller Ingress default/laravel-kubernetes-demo-ingress Normal UPDATE 20s nginx-ingress-controller Ingress default/laravel-kubernetes-demo-ingress
You can now access the application through the minikube IP address as shown above. To access the application through the URL https://laravel-kubernetes.demo, you will need to add an entry in your hosts file.
This is just the beginning
Special thanks to Daniele Polencic , I couldn't of written this article without your help 🙏
Have you enjoyed reading this article?
Don't be selfish, share it with your friends 😉
Got questions or feedback? Leave a comment, I will reply.