ae03f22c65
Automatic merge from submit-queue (batch tested with PRs 45949, 46009, 46320, 46423, 46437) Implement audit policy logic Includes https://github.com/kubernetes/kubernetes/pull/45315#discussion_r117115932 (ignore the first commit) Feature: https://github.com/kubernetes/features/issues/22 Remaining work: - [x] Load the policy into the `server.Config` - [x] Rebase on https://github.com/kubernetes/kubernetes/pull/45315 - [x] Establish shared code for audit api scheme (with https://github.com/kubernetes/kubernetes/pull/45919) - [x] Once https://github.com/kubernetes/kubernetes/pull/45766 is merged, call the policy checker in the audit path /cc @sttts @soltysh @ericchiang @ihmccreery @pweil- @deads2k
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.