Aggregator for Kubernetes-style API servers: dynamic registration, discovery summarization, secure proxy
Switch branches/tags
Clone or download
k8s-publishing-bot Merge pull request #71785 from sttts/sttts-aggregator-condition-time
aggregator: fix available condition transition time

Kubernetes-commit: 16fb54ef7c10e3865ef5f0af69b2479a084b85c5
Latest commit 06e74d1 Dec 7, 2018

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.