49bee177b2
Automatic merge from submit-queue (batch tested with PRs 49115, 47480) Upgrade advanced audit to version v1beta1 This change does nothing but only upgrades advanced audit to version v1beta1. There will be following up changes which does real effect to advanced audit feature. After this change audit policy file should contain apiVersion and kind and has such format: ``` apiVersion: audit.k8s.io/v1alpha1 kind: Policy rules: - level: None ``` or use the v1beta1 policy: ``` apiVersion: audit.k8s.io/v1beta1 kind: Policy rules: - level: None ``` Updates #48561 **Release note**: ``` Upgrade advanced audit to version v1beta1. ```
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/kube-gen(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>.