Lee Verberne e10042d22f Increment CRI version from v1alpha1 to v1alpha2 ...

This also incorporates the version string into the package name so
that incompatibile versions will fail to connect.

Arbitrary choices:
- The proto3 package name is runtime.v1alpha2. The proto compiler
  normally translates this to a go package of "runtime_v1alpha2", but
  I renamed it to "v1alpha2" for consistency with existing packages.
- kubelet/apis/cri is used as "internalapi". I left it alone and put the
  public "runtimeapi" in kubelet/apis/cri/runtime.

2018-02-07 09:06:26 +01:00

..

BUILD

Increment CRI version from v1alpha1 to v1alpha2

2018-02-07 09:06:26 +01:00

fake_cache.go

start the apimachinery repo

2017-01-11 09:09:48 -05:00

fake_runtime_helper.go

Increment CRI version from v1alpha1 to v1alpha2

2018-02-07 09:06:26 +01:00

fake_runtime.go

run hack/update-all

2017-06-22 11:31:03 -07:00

mock_runtime_cache.go

Change StatsProvider interface to provide container stats from either cadvisor or CRI and implement this interface using cadvisor

2017-08-25 13:11:26 -07:00

mockfileinfo.go

Add pod log garbage collection unit test.

2016-10-24 00:03:34 -07:00

os.go

Use chmod to bypass umask on termination log file

2017-01-23 12:26:37 -05:00

runtime_mock.go

run hack/update-all

2017-06-22 11:31:03 -07:00