All Blog Posts for Cluster-Computing

  • High availability (Multi-master) Kubernetes cluster hosted on AWS

    High availability (Multi-master) Kubernetes cluster hosted on AWS

        This is a first post of a mini-series dedicated to running Kubernetes hosted on AWS. First post will be about the considerations we have made when proposing production ready and Enterprise grade Kubernetes environment to our clients. I will go more technical, with the tools and AWS services we are using, in the next blog post, here I will try to cover what problems we are solving.     High availability is a characteristic we want our system to have. We aim to ensure an agreed level of operational performance (uptime) for a higher than normal period. These are the principles we follow when doing the system design:  - Elimination of single points of failure. This means adding redundancy to the system so that failure of a component does not mean failure of the entire system.  - Reliable crossover. In redundant systems, the crossover point itself tends to become a single point of failure. Reliable systems must provide for reliable crossover.  - Detection of failures as they occur. If the two principles above are observed, then a user may never see a failure. But the maintenance activity must.        Below graph shows the Kubernetes Master components used for setting up a cluster. Will go thorough them one by one :