test.

Automatic merge from submit-queue

updates to vagrant.md

Addresses issue #24259; merges in edits from the now deleted version of vagrant.md from the kubernetes.github.io/docs/getting-started-guides directory see PR 
https://github.com/kubernetes/kubernetes.github.io/pull/294Signed-off-by: mikebrow <brownwm@us.ibm.com>

Fix verification script for proto-generation

Automatic merge from submit-queue

make storage enablement, serialization, and location orthogonal

This allows a caller (command-line, config, code) to specify multiple separate pieces of config information regarding storage and have them properly composed at runtime.  The information provided is exposed through interfaces to allow alternate implementations, which allows us to change the expression of the config moving forward.  I also fixed up the types to be correct as I moved through.

The same options still exist, but they're composed slightly differently
 1. specify target etcd servers per Group or per GroupResource
 1. specify storage GroupVersions per Groups or per GroupResource
 1. specify etcd prefixes per GroupVersion or per GroupResource
 1. specify that multiple GroupResources share the same location in etcd
 1. enable GroupResources by GroupVersion or by GroupResource whitelist or GroupResource blacklist

The `storage.Interface` is built per GroupResource by:
 1. find the set of possible storage GroupResource based on the priority list of cohabitators
 1. choose a GroupResource from the set by looking at which Groups have the resource enabled
 1. find the target etcd server, etcd prefix, and storage encoding based on the GroupResource

The API server can have its resources separately enabled, but for now I've kept them linked.

@liggitt I think we need this (or something like it) to be able to go from config to these interfaces.  Given another round of refactoring, we may be able to reshape these to be more forward driving.

@smarterclayton this is important for rebasing and for a seamless 1.2 to 1.3 migration for us.

Automatic merge from submit-queue

Increase provisioning test timeouts.

We've encountered flakes in our e2e infrastructure when kubelet took more than one minute to detach a volume used by a deleted pod.

Let's increase the wait period from 1 to 3 minutes. This slows down the test by 2 minutes, but it makes the test more stable.

In addition, when kubelet cannot detach a volume for 3 minutes, let the test wait for additional recycle controller retry interval (10 minutes) and hope the volume is deleted by then. This should not increase usual test time, it makes the test stable when kubelet is _extremely_ slow when releasing the volume.

Fixes: #24161

Automatic merge from submit-queue

etcd3 store: provide compactor util

What's this PR?
- Provides a util to compact keys in etcd.

Reason:
We want to save the most recent 10 minutes event history. It should be more than enough for slow watchers. It is not number based, so it can tolerate event bursts too. We do not want to save longer since the current storage API cannot take advantage of the multi-version key yet. We might keep a longer history in the future.

Automatic merge from submit-queue

Allow Proxy to be initialized with store

Automatic merge from submit-queue

Remove requirement that Endpoints IPs be IPv4
Signed-off-by: André Martins <aanm90@gmail.com>

Release Note: The `Endpoints` API object now allows IPv6 addresses to be stored.  Other components of the system are not ready for IPv6 yet, and many cloud providers are not IPv6 compatible, but installations that use their own controller logic can now store v6 endpoints.

Generate protobuf marshallers for new apps group

Automatic merge from submit-queue

watcher test: print more info for debugging

ref: #24528

This will print out more info to dig out the root cause.

Automatic merge from submit-queue

Apigroup and alpha resource for petset

I'm still writing unittests, validation and comments but I'm planning to punt on anything more involved since this is alpha. 

@smarterclayton @bgrant0607 @thockin probably only care about first commit. I'm hoping we can take this as a rough cut and iterate. 

@lavalamp for general api machinery

Automatic merge from submit-queue

Disable flannel job until it works

https://github.com/kubernetes/kubernetes/issues/24520

See bug, this job is fails every time and has done so for two months. Until someone has time to investigate and fix disable the job on jenkins so we're not wasting resources and reducing system stability.

Automatic merge from submit-queue

Enable protobuf compilation by default

Enables protobuf compilation, build verification checks, and generates all initial code.

kubectl is now 47M on OSX, build time from clean on a 2014 MBP (4 core) on Go 1.6 is ~150s.

@wojtek-t

Automatic merge from submit-queue

Add locks in HPA test

Fixes #23361

Automatic merge from submit-queue

hack: change update-swagger-spec.sh apiserver defaults

Removing the explicit list of KUBE_API_VERSIONS will cause the apiserver
to enable all APIs by default. This change reduces the amount of script
hacking needed to add new API groups in the future.

Automatic merge from submit-queue

Fix so make == make push in the kube-cross Makefile

ref: https://github.com/kubernetes/kubernetes/pull/23931#issuecomment-210120719
@david-mcmahon 

Signed-off-by: mikebrow <brownwm@us.ibm.com>

Automatic merge from submit-queue

Fix gs:// path to kubernetes binary in 1.3.0-alpha.2.

ref #24535 #24534

Automatic merge from submit-queue

Enable go vet.

Automatic merge from submit-queue

etcd3/store: support TTL in Create, Update

ref: https://github.com/kubernetes/kubernetes/issues/22448

What's included in the PR?
- Support TTL keys in Create() and Update()
- Simple testing for create

Note
- Have TTL keys in a long window (5min) in one lease. I'm not sure if we should do it right now. We could just implement it as simple as is. Once we have etcd3 work done we could start testing and measuring with some realistic load.

Automatic merge from submit-queue

Proposal for improving local cluster experience.

This proposal attempts to improve the existing single node, local cluster experience in Kubernetes.

It is **not** a proposal that helps with setting up a multi-node, production cluster.

cc @dlorenc  @ethernetdan @runseb @mfburnett @bgrant0607 @pwittrock 

Automatic merge from submit-queue

client-gen: use serializer instead of codec for versioned client

For a versioned client, because the output of every client method is a versioned object, so it should use a serializer instead of a codec that does conversion.

@lavalamp @krousey 

Automatic merge from submit-queue

Trusty: Handle the new var in kube-proxy manifest

This is to capture the kube-proxy manifest change in PR #24429.

@roberthbailey @fabioy @zmerlynn please review this change and mark it as cherry pick candidate. We need to catch up 1.2.3 release.

cc/ @dchen1107 @wonderfly @cjcullen FYI.

I have verified this fix. Without this fix, kube-proxy pod in Trusty nodes cannot be started correctly, i.e., the command line has an unhadled variable. And some other kube-system pods do not work correctly as kube-proxy is not working well. After applying this fix, kube-proxy can be started correctly, and all kube-system pods run successfully. 

Automatic merge from submit-queue

Fix GLBC cluster addon README link

Fix the link to L7 load balancer controller in GLBC cluster addon README.

Fixed #24462.