0076f02df0
Automatic merge from submit-queue (batch tested with PRs 51603, 51653) Graduate metrics/v1alpha1 to v1beta1 This introduces v1beta1 of the resource metrics API, previously in alpha. The v1alpha1 version remains for compatibility with the Heapster legacy version of the resource metrics API, which is compatible with the v1alpha1 version. It also renames the v1beta1 version to `resource-metrics.metrics.k8s.io`. The HPA controller's REST clients (but not the legacy client) have been migrated as well. Part of kubernetes/features#118. ```release-note Migrate the metrics/v1alpha1 API to metrics/v1beta1. The HorizontalPodAutoscaler controller REST client now uses that version. For v1beta1, the API is now known as resource-metrics.metrics.k8s.io. ```
External Repository Staging Area
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.
Repositories currently staged here:
k8s.io/apiextensions-apiserverk8s.io/apik8s.io/apimachineryk8s.io/apiserverk8s.io/client-gok8s.io/kube-aggregatork8s.io/code-generator(about to be published)k8s.io/metricsk8s.io/sample-apiserver
The code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code.
Using staged repositories from Kubernetes code
Kubernetes code uses the repositories in this directory via symlinks in the
vendor/k8s.io directory into this staging area. For example, when
Kubernetes code imports a package from the k8s.io/client-go repository, that
import is resolved to staging/src/k8s.io/client-go relative to the project
root:
// pkg/example/some_code.go
package example
import (
"k8s.io/client-go/dynamic" // resolves to staging/src/k8s.io/client-go/dynamic
)
Once the change-over to external repositories is complete, these repositories
will actually be vendored from k8s.io/<package-name>.