Library for writing a Kubernetes-style API server.
Go to file
Christoph Blecker 64f3b76260 Update generated files
Kubernetes-commit: 4361a9146e34d74fce9c0193b11b920ffbd0eda8
2017-05-18 17:28:00 +00:00
Godeps sync: resync vendor folder 2017-05-17 17:28:28 +00:00
hack handle resetting godep.json for resync 2017-02-23 11:14:39 -05:00
pkg Update generated files 2017-05-18 17:28:00 +00:00
plugin/pkg hack/update-bazel.sh 2017-05-13 17:27:43 +00:00
vendor sync: resync vendor folder 2017-05-17 17:28:28 +00:00
.import-restrictions move pkg/auth/user to staging 2017-01-13 13:38:43 -05:00
LICENSE add readme and license 2017-01-13 13:29:55 -05:00
OWNERS Update my OWNERS entries. 2017-03-31 20:37:16 +00:00
README.md update link for kube-aggregator 2017-05-01 15:47:40 -07:00
kubernetes-sha sync(k8s.io/kubernetes) 8902dae1c4e12a0b5933beb965b148b4150c970d 2017-05-17 17:27:53 +00:00

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 comsumers 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

  1. Directly modify any files under pkg in this repo. Those are driven from k8s.io/kuberenetes/staging/src/k8s.io/apiserver.
  2. Expect compatibility. This repo is changing quickly in direct support of Kubernetes and the API isn't yet stable enough for API guarantees.