This article is currently an experimental machine translation and may contain errors. If anything is unclear, please refer to the original Chinese version. I am continuously working to improve the translation.
During summer vacation, I took advantage of my credit card to enjoy some free credits from GCP. Since there’s still a fair amount left before expiration, I decided to give K8s cluster deployment a try.
I attempted using Kuboard-Spray for deployment, along with the Kuboard management dashboard. (Both official guides and tutorials are very detailed~)
Following the official links above, setting up a production-ready K8s cluster was quite straightforward.
K8s Cluster Deployment
The whole process took nearly 20 minutes. From the logs, I could see that Kuboard-Spray had already handled many tedious configurations behind the scenes.
Side note: K8s really carries on Google’s tradition of complexity—definitely a test of one’s skills and patience (compare with the notoriously hard-to-read official docs).
After the K8s cluster was up, Kuboard was automatically deployed as well. Accessing port 80 on the Master node brings you to the management UI.
Kuboard
The interface is significantly more complex than Kube-explorer I’ve used before—seems better suited for managing large-scale distributed applications.
Since my personal use cases can still be handled by Docker Swarm, I didn’t dive any deeper for now…
I’ll probably come back to explore the full power of K8s once I’ve learned Spring Cloud.
This article is licensed under the CC BY-NC-SA 4.0 license.
Author: lyc8503, Article link: https://blog.lyc8503.net/en/post/k8s-setup/
If this article was helpful or interesting to you, consider buy me a coffee¬_¬
Feel free to comment in English below o/