Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Make audit output version configurable. This is a re-make of https://github.com/kubernetes/kubernetes/pull/51786, taken over form @soltysh Copying from the previous PR: This is followup to https://github.com/kubernetes/kubernetes/pull/51719 to start the discussion how we want to solve the problem of users picking which version is being served them. We need to have an option for log and webhook, separately. Probably, for webhook backend with multiple destinations we'd like to send different version to each. This approach adds two flags (only the second commit matters), one for log and another for webhook (unfortunately global one). I've looked into kubeconfig types and although there are options to specify group and version they are meant for removal. @liggitt had some thoughts maybe he could share the ideas and we can pick it up here. @ericchiang @CaoShuFeng @sttts opinions, thoughts are more than welcome ```release-note Add apiserver configuration option to choose audit output version. ``` Kubernetes-commit: 52ed0368f8d076236ada19b09828f2f9e2ebb6ef |
||
---|---|---|
.github | ||
Godeps | ||
pkg | ||
plugin/pkg | ||
vendor | ||
.import-restrictions | ||
LICENSE | ||
OWNERS | ||
README.md | ||
code-of-conduct.md |
README.md
apiserver
Generic library for building a Kubernetes aggregated API server.
Purpose
This library contains code to create Kubernetes aggregation server complete with delegated authentication and authorization,
kubectl
compatible discovery information, optional admission chain, and versioned types. It's first consumers are
k8s.io/kubernetes
, k8s.io/kube-aggregator
, and github.com/kubernetes-incubator/service-catalog
.
Compatibility
There are NO compatibility guarantees for this repository, yet. It is in direct support of Kubernetes, so branches will track Kubernetes and be compatible with that repo. As we more cleanly separate the layers, we will review the compatibility guarantee. We have a goal to make this easier to use in 2017.
Where does it come from?
apiserver
is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver.
Code changes are made in that location, merged into k8s.io/kubernetes
and later synced here.
Things you should NOT do
- Directly modify any files under
pkg
in this repo. Those are driven fromk8s.io/kubernetes/staging/src/k8s.io/apiserver
. - Expect compatibility. This repo is changing quickly in direct support of Kubernetes and the API isn't yet stable enough for API guarantees.