github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '50227ff894'
${ noResults }
k3s/vendor/k8s.io/kube-aggregator
History
Erik Wilson 94760b1ecb
Update k8s to v1.14.6-k3s.1 		5 years ago
..
pkg Update k8s to v1.14.6-k3s.1 5 years ago
BUILD Update vendor 6 years ago
CONTRIBUTING.md Update vendor 6 years ago
LICENSE Update vendor 6 years ago
OWNERS Update vendor 6 years ago
README.md Update vendor 6 years ago
SECURITY_CONTACTS Update vendor 6 years ago
code-of-conduct.md Update vendor 6 years ago

README.md

kube-aggregator

Coming Soon!

Implements https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/aggregated-api-servers.md.

It provides

  • Provide an API for registering API servers.
  • Summarize discovery information from all the servers.
  • Proxy client requests to individual servers.

Purpose

We want to divide the single monolithic API server into multiple aggregated servers. Anyone should be able to write their own aggregated API server to expose APIs they want. Cluster admins should be able to expose new APIs at runtime by bringing up new aggregated servers.

Compatibility

HEAD of this repo will match HEAD of k8s.io/apiserver, k8s.io/apimachinery, and k8s.io/client-go.

Where does it come from?

kube-aggregator is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kube-aggregator. Code changes are made in that location, merged into k8s.io/kubernetes and later synced here.