Martin Podval' Streamlog

I have been working with Kubernetes and I wanted to build it's contrib yesterday. However, nginx implementation of Kubernetes' Ingress is written in go-lang . Even though I needed to change some  const string , it required recompilation. Go is not java, and go building system is not maven. Setting up the environment was not straightforward. I was facing couple troubles but I'm going to take it from the beginning. My laptop uses ubuntu 15.04 - well 15.10 since 9pm :-) - and I have never installed go lang yet. Go lang installation on Ubuntu First of all, you need to install go lang. You can use official repo , but it contains older version 1.3. However, do not install it using apt-get as kubernetes or it's dependencies require higher version of go-lang. Of course, I originally installed version 1.3  but some fatal error occurred later. It forced me do to the manual installation anyway. Here is simple tutorial . Last two lines affect only the current termin

I'd like to deal in this part with potential benefits resulting from using CoreOS as an operating system in your cloud deployment. You can install kubernetes on various operating systems  so you can make a decision what to choose. So why CoreOS? What is my experience? Etcd, Fleet and Flannel Preinstalled First reason is obvious. CoreOS always provides latest version of all components in Kubernetes cluster.  My experience : we have profited from pre-installed components from the beginning. E.g. in early stages when etcd was coming with new beautiful and powerful API (v.2), they put both - old and new - versions together so we just enabled one of them. The setup of all components together is not very simple so you can save couple hours by choosing preinstalled and pre-setuped CoreOS. No Package Manager, Read Only Partitions It sounds more like disadvantage than benefit, but ... Look at CoreOS releases what it consist of. Fore example, CoreOS includes basic

We were lucky enough in December 2014 to join the group of teams who use CoreOS stack and Kubernetes on their way to become next generation of cloud infrastructure . It has been almost one year so I'd like to provide a article series about our experience with the whole stack. The Motivation You usually want to model your business domain, provide useful APIs, break your application into pieces, services , and so on. Well, it's your work. The distributed computing is one of most challenging disciplines in the computer science. Why is that? Because of an asynchronicity in the form of remote calls among distributed components. There are no locks like in your favorite languages. However, there are remote calls with no guarantees of any response or in any time. It's pretty challenging to provide high-available application, with no downtime during updates, crashes. The application which scales according to the needs. The application with guarantees any data consistency.