WIP: Add election framework to master; publish services.

Needs tests still.
Making apiserver master-elected will make it simpler to maintain coherent
indexes for validation.

I also don't have a picture of how you would to admission control (quota)
in a stateless fashion.

Also, what is going to allocate IP addresses for services?  It seems like
the apiserver does that, and it needs state for the next available address?

On Tue, Oct 21, 2014 at 8:17 AM, Clayton Coleman <notifications@github.com>
wrote:

> In pkg/master/publish.go:
>
> > +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > +See the License for the specific language governing permissions and
> > +limitations under the License.
> > +*/
> > +
> > +package master
> > +
> > +import (
> > +	"time"
> > +
> > +	"github.com/GoogleCloudPlatform/kubernetes/pkg/api"
> > +
> > +	"github.com/golang/glog"
> > +)
> > +
> > +func (m *Master) serviceWriterLoop(stop chan struct{}) {
>
> How does another process (like a component plugin) emulate this behavior?
> I'd like to discuss the direction for this because we are very dependent on
> being able to work well with this and the transition plan worries me a bit
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/kubernetes/pull/1920/files#r19154674>
> .
>