While preparing the CKA exam, I have been using minikube and kubeadm or Rancher’s rke to bootstrap kubernetes clusters. Those tools are very nice but I wanted to understand all the details of a full setup. The best for this is the excellent “Kubernetes The Hard Way” tutorial from Kelsey Hightower.
When I decided to start blogging and have my own “site”, I chose Wordpress.com as it is was for me the easiest and most comfortable solution. I have been using it for a few month and to be fair, I think the product and service are ok.
gRPC is an open source RPC framework offering high performance and pluggable support for authentication, tracing, health checks and load balancing. It offers libraries in most widely used languages (Java, Node.js, C++, Python, Go,..)
gomotics is a Go API for Niko Home Control.
Rancher Labs has released Rancher 2.0 Tech Preview on 26th of September. The 2.0 release is a significant one as it brings many changes compared to 1.x versions. Based on current Rancher users feedback, market trends (almost all major infrastructure providers offer “Kubernetes-As-A-Service”), and some vision (“Kubernetes everywhere”), they have re-engineered Rancher 2.0 to be fully based on Kubernetes.
In the previous post, I was introducing my personal project “gomotics”, a domotics API for Niko Home Control, written in Go. In this post I will detail how I setup the “build – test – release” pipeline for this project.
I am developing a small domotics back-end in Go, mainly as a learning method. I already did that in NodeJs and as I wanted to learn Golang, I decided to re-develop same kind of tool. This time, I am doing it more “properly” in terms of testing coverage. And as Go is a compiled language, I have setup an automated build, test and release process using Travis CI, Coveralls and goreleaser. Those tools are amazing!
If you don’t mind my interesting story, scroll down to the “quick demo overview” 😉
This post has also been published on Rancher.com on 12-07-2017