The last article of the series “Kubernetes and everything else”, here we tie everything together once and for all, we cover everything from code and up to the deployment in Kubernetes. And some closing words for going together through the series.
Kubernetes Deployments help us with one constant in the life of every application, and that is change. Moreover, the only applications that do not change are the ones that are already dead, and while not, new requirements will come in, more code will be shipped, it will be packaged, and deployed. And on each step
In the last article Kubernetes in Practice – Pods, we started two pods (sa-frontend and sa-frontend2) and we were left with two requirements, which will be the topic of this article: Exposing the services (running in the pods) externally, and Load balancing between them. The Kubernetes Service resource acts as the entry point to a set of
We covered how to run the Microservices in separate containers in these two articles Container-ization of the Services and Container-ization of everything else, and it was a cumbersome process, but it worked (see fig. 1.). Additionally, we mentioned that this solution is not scalable or resilient and that Kubernetes will resolve these issues. So in this article
What is Kubernetes, what are the features it has and as always explained simply. This part is a continuation of the Series “Kubernetes and everything else” that builds an microservice application up, containerizes it and then deploys it to Kubernetes. Best source to learn Kubernetes and the context it is in.
Let’s continue where we left off, creating the Images for the Java and Python Applications. And then we will verify that everything works together. Then we are ready to continue with the most important part Kubernetes.
Learn Docker basics and how to define, build and push your docker container that serves static files using the Nginx WebServer. This article is from the “Kubernetes and everything else” series and will be of prime importance to understand how Kubernetes works.
To start the Python application we need to have Python3 and Pip installed (their environment variables need to be set up as well). Installing Dependencies Navigate in the CMD to the directory sa-logic/sa (repo) and type the following command: $ python -m pip install -r requirements.txt $ python -m textblob.download_corpora Starting the app Pip installs the dependencies
To start up the Spring application we need to have JDK8 and Maven installed (their environment variables need to be set up as well). After installing those we will continue to the next part. Packaging the Application into a Jar Navigate in your Terminal to the directory sa-webapp (repo) and type the following command: $ maven