# DevOps(Day-84): Project-5 : Netflix application ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707856098238/14370318-5a6d-4f10-aab6-d03e8c730d43.png align="center") ## [**Pr**](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-pre-requisites)[**oject Descript**](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-project-description)[**ion**](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-pre-requisites) [The project i](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-project-description)[nvolves deplo](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-pre-requisites)[ying a Netfli](https://bandandevopsjourney.hashnode.dev/devopsday-84-project-5-netflix-application#heading-project-steps)x clone web application on a Kubernetes cluster, a popular container orchestration platform that simplifies the deployment and management of containerized applications. The project will require creating Docker images of the web application and its dependencies and deploying them onto the Kubernetes cluster using Kubernetes manifests. The Kubernetes cluster will provide benefits such as high availability, scalability, and automatic failover of the application. Additionally, the project will utilize Kubernetes tools such as Kubernetes Dashboard and kubectl to monitor and manage the deployed application. Overall, the project aims to demonstrate the power and benefits of Kubernetes for deploying and managing containerized applications at scale. ## **Pre-requisites** 1. Create an EC2 instance with t2.medium configuration in the AWS management console. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707854668593/fc7b7732-259e-416e-91ad-f3b358229add.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707854703582/a521abc2-fd36-474b-907b-121248fdce23.png align="center") 2. Install docker in the EC2 instance. Check the running status in the server. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707854767895/f5f1d938-6c99-4b5d-bc63-0ffcef2bcced.png align="center") 3. Install kubernetes in the EC2 instance along with kubectl utility in the server. You can follow my previous Kubernetes blog in the below link:- [https://lokeshdevopsblog.hashnode.dev/day-31-task-launching-your-first-kubernetes-cluster-with-nginx-running](https://lokeshdevopsblog.hashnode.dev/day-31-task-launching-your-first-kubernetes-cluster-with-nginx-running) 4. Check the kubectl installation status in the server. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707854943549/ce7f678a-3916-44ae-8985-9c7e64304806.png align="center") ## **Project steps** 1. Get code from GitHub and clone in the EC2 instance. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855046058/15590375-8d6d-4c4f-aca4-83277ae6ef9b.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855147038/3bea9d2e-be3b-48ee-a1e0-3fd25bd7e7d5.png align="center") 2. Make sure you have already written the docker file. Create an image out of docker file and create and run the container out of it. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855227719/2a0aa7f7-ce42-4207-9152-8f2f0636efee.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855279782/ca2b0813-bc84-44b1-8caf-f1890fbb5640.png align="center") 3. Push the image to the DockerHub repository. You can follow my previous docker blogs to get the detailed seps. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855390833/17766b1e-831c-4427-885f-11855d45ce64.png align="center") 4. Now, create the deployment yaml file. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855447617/6445de30-fd6b-4b4e-b701-af6e76d0ab8e.png align="center") 5. Run and check the successful running of deployment in the instance. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855566139/c5f27410-3f66-4cfb-acbd-47d980170512.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855648685/95fbbbde-ed19-47a3-b8bc-fc8c57817b32.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855685194/6d4a81ba-14d3-418f-b0a7-54782effdead.png align="center") 6. Create a service.yaml file to connect the node port and access the url from the outside world. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855767428/66739f37-a2b2-43bb-9bca-2a6ebdc598c1.png align="center") 7. Run and check the successful running of service in the instance. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855861281/b5190d18-9f51-4f71-9193-428d4f38d7e5.png align="center") 8. Get the URL and curl it to check the website accessibility. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707855960742/c47299c3-7fab-40d1-b65d-357e5025131d.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707856034782/8c92cfdb-3f99-4d83-af5e-af456e05b93d.png align="center") 9. Check with Public URL and we can now see the Netflix APP running on the pour server. ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707856098238/14370318-5a6d-4f10-aab6-d03e8c730d43.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707856147083/b4bb8d0a-00ff-4fc1-af55-8b472a830b48.png align="center") ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1707856184128/4287e094-2450-4fe9-a58e-bfb402720e08.png align="center") 10. This Netflix app shows all the current data running on the actual Netflix app. This is achieved by configuring API key while creating the container. You can follow the [**readme.md**](https://github.com/Bandank/netflix-clone-react-typescript/blob/main/README.md) file in the GitHub repository. Thanks for reading my article. Have a nice day. Happly Learning Lokesh Telange ✨✨