Skip to content
Aggregator for Kubernetes-style API servers: dynamic registration, discovery summarization, secure proxy
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
Godeps
artifacts remove unused rls-ca-file flag Mar 20, 2018
hack
pkg
vendor Merge pull request #75270 from justincormack/uuid4 Mar 22, 2019
CONTRIBUTING.md
LICENSE Add README and LICENSE to staging repos Oct 23, 2017
OWNERS
README.md Add README and LICENSE to staging repos Oct 23, 2017
SECURITY_CONTACTS Also update SECURITY_CONTACTS from staging Mar 8, 2019
code-of-conduct.md Add code-of-conduct.md to staging repos Dec 20, 2017
main.go move logs into component-base Jan 17, 2019

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.

You can’t perform that action at this time.