99aa992ce8
Automatic merge from submit-queue (batch tested with PRs 51186, 50350, 51751, 51645, 51837) Update Cadvisor Dependency Fixes: https://github.com/kubernetes/kubernetes/issues/51832 This is the worst dependency update ever... The root of the problem is the [name change of Sirupsen -> sirupsen](https://github.com/sirupsen/logrus/issues/570#issuecomment-313933276). This means that in order to update cadvisor, which venders the lowercase, we need to update all dependencies to use the lower-cased version. With that being said, this PR updates the following packages: `github.com/docker/docker` - `github.com/docker/distribution` - `github.com/opencontainers/go-digest` - `github.com/opencontainers/image-spec` - `github.com/opencontainers/runtime-spec` - `github.com/opencontainers/selinux` - `github.com/opencontainers/runc` - `github.com/mrunalp/fileutils` - `golang.org/x/crypto` - `golang.org/x/sys` - `github.com/docker/go-connections` - `github.com/docker/go-units` - `github.com/docker/libnetwork` - `github.com/docker/libtrust` - `github.com/sirupsen/logrus` - `github.com/vishvananda/netlink` `github.com/google/cadvisor` - `github.com/euank/go-kmsg-parser` `github.com/json-iterator/go` Fixed https://github.com/kubernetes/kubernetes/issues/51832 ```release-note Fix journalctl leak on kubelet restart Fix container memory rss Add hugepages monitoring support Fix incorrect CPU usage metrics with 4.7 kernel Add tmpfs monitoring support ```
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>.