Learning Kubernetes with Minecraft Servers
Since i was 14 years old, i have been developing Spigot, BungeeCord plugins, and consequently handling Linux based servers.
In spigot plugins you have to create SQL queries,consume web apis, take care of server FPS, create a database structure, create proxies, and others.
In a minecraft network you have multiple services depending in each other, and still you have to scale minecraft instances depending on the amount of players connected to the network, dealing with this manually or even with scripts is a pain in the ass, so i need to look for another solution.
Due to the complexity of a minecraft network, and the need for scalability, K8s is the perfect solution for this problem.
So i want to combine the business with pleasure, and start to learning K8s to resolve this problem. My intend is to arquitect cluster to handle at the same time, Minecraft server instances, Web APIs, databases, caches, proxies, CI/CD, Repositories, and others.
Send a mail to [email protected]
In this project i'm using minikube because my object is to understand the concepts of K8s and after learn how to configure a cluster from scratch.
Since is much easy to remember domains rather than ips, i'm using dnsmasq to point all *.minikube domains to the minikube vm, and with this method is also much easier to setup ingresses. This was accomplished with adding this line in /etc/dnsmasq.conf.
# you can get your vm address with the command 'minikube ip'
address=/.minikube/192.168.39.54
minikube addons enable ingress
Before starting to deploying images to the registry, you need to allow the docker.nexus.minikube unsecure registry in your machine.
More information can be found here.
You also need to login with the default credentials
# Username: developer
# Password: 123
docker login docker.nexus.minikube# You can create the resources with
cd /ci
kubectl apply -k .
# Then you need to provide the registry auth secret to the default service account
kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "regcred"}]}'I am using the jenkins kubernetes plugins, when a job is dispatched the plugin create automatically a pod to run it.
The configuration is done through the Configuration as Code Plugin
You have to push the docker image before creating the statefulset, just execute the pushImage.sh script.
- URL: http://jenkins.minikube
- User: admin
- Password: 123
Maven repository to store artifacts, the configuration is done automatically through groovy scripts.
Using my own nexus3 image, that can be found HERE.
- URL: http://nexus.minikube
- User: admin
- Password: 123