Skip to main content

Today we're excited to announce that official CoreOS images are available on Google Compute Engine. This means it's now even easier to spin up a CoreOS cluster on GCE using the API or from the command line. Adding an instance is as simple as:

The etcd team has been focused on making it easier to scale and manage larger clusters, and is happy to announce a release with features to help: etcd v0.4.0. This release is an important step in our road to 1.0. (If you are new to etcd, our getting started guide can give you a quick overview of the project).

Update: Vulcand has been updated since this post was written. Jump to https://github.com/vulcand/vulcand for more info. You can follow the concepts of this post, but the commands are no longer up to date.

Running a distributed system across many machines requires a sophisticated load balancing mechanism that can reconfigure itself quickly and reliably.

After 150 releases and 9 months in alpha, we are excited to announce the first CoreOS beta. Starting today, we will be releasing both alpha and beta versions of CoreOS. The beta means you can expect CoreOS itself to not change in any significant way, and it should be considered close to production-ready.

The beta includes a new feature, Locksmith, giving you control over the CoreOS update process, as well as a variety of bug fixes and feature enhancements.

When you're first exposed to a distributed platform like CoreOS, running a development environment that is complex enough to match production seems like an impossible task. This article is going to show you how convienient it is run a small CoreOS cluster on your local machine with Vagrant that will mirror the way your production machines are set up.

Over the last few months the extent of community involvement and adoption of etcd has surpassed all our expectations. We wanted to take this opportunity to share with the wider community our plan for the ongoing development of etcd.

We want etcd to be a stable base for you to build distributed systems that are resilient to failures. Users of etcd should find things consistent and predictable, and client libraries should not need to be updated for years. In short, we need to get to 1.0, and this is clearly not where etcd is today.

We locked the CoreTeam in a house for a week to make this release extra special. Here are all the new features:

The ambassador pattern is a novel way to deploy sets of containers that are configured at runtime via the Docker Links feature.

As of version 210, systemd now includes support for basic network configuration through udev and networkd. CoreOS sponsored the development of networkd. It will soon be available in CoreOS, so we would like to take the opportunity to introduce some of its features.

Today I'd like to introduce our latest project, fleet. fleet builds on etcd and systemd to provide a distributed, fault-tolerant platform for deploying applications on CoreOS clusters.

Subscribe to CoreOS Blog