kubernetes

Files

Kubernetes Submit Queue ae1ff1a2d4 Merge pull request #48746 from janetkuo/apps-v1beta2

Automatic merge from submit-queue

Add a new API version apps/v1beta2

xref: #49135
This PR adds a new API version `apps/v1beta2` which contains a copy (of types, conversions, and defaults) of `apps/v1beta1` StatefulSet, Deployment, and their subresources. Note that `apps/v1beta2` is still WIP and we will make breaking changes to it before releasing 1.8.

Moving core controllers (StatefulSet, Deployment, ReplicaSet, DaemonSet) to `apps/v1beta2` is the first step of moving them to `apps/v1` (GA). 

This PR is a starting point for DaemonSet and ReplicaSet to move from `/extensions` to `/apps` and for Deployment and StatefulSet to make some breaking changes (e.g. new defaults and/or remove deprecated fields).

```release-note
Add a new API version apps/v1beta2
```

2017-07-21 11:47:21 -07:00

src/k8s.io

Merge pull request #48746 from janetkuo/apps-v1beta2

2017-07-21 11:47:21 -07:00

copy.sh

Merge pull request #49116 from sttts/sttts-authorative-api-v1-ref

2017-07-19 03:21:25 -07:00

godeps-json-updater.go

Clean up staging/godeps-json-updater.go

2017-04-06 09:32:57 +02:00

OWNERS

Add OWNERS for staging and api

2017-04-19 15:58:09 -04:00

prime-apimachinery.sh

Fixup go2idl references

2017-07-20 07:41:37 +02:00

README.md

Update staging README to reflect multiple repos

2017-05-12 13:19:50 -07:00

README.md

This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.

Most code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code. However the packages in staging/src/k8s.io/client-go/pkg are copied from pkg/. If you modify the original code in pkg/, you need to run hack/godep-restore.sh from the k8s root directory, followed by hack/update-staging-client-go.sh. We are working towards making all code in staging/ authoritative.

The vendor/k8s.io directory contains symlinks pointing to this staging area, so to use a package in the staging area, you can import it as k8s.io/<package-name>, as if the package were vendored. Packages will be vendored from k8s.io/<package-name> for real after the test matrix is converted to vendor k8s components.