Library for writing a Kubernetes-style API server.
Go to file
M.B.S. Sai Akhil a9b50ab329 Fix Typo in apiserver README
Kubernetes-commit: 5e9704572fe28650d15a40de60859a931c0d4f7e
2018-01-07 08:45:11 +05:30
Godeps Merge pull request #56769 from dixudx/forbid_unnamed_context 2018-01-07 19:53:34 +00:00
pkg forbid unnamed context 2017-12-04 14:39:05 +08:00
plugin/pkg Autogenerate BUILD files 2017-12-23 13:06:26 -08:00
vendor Merge pull request #57480 from jpbetz/etcd-client-3.2.12 2018-01-07 19:52:32 +00:00
.import-restrictions move pkg/auth/user to staging 2017-01-13 13:38:43 -05:00
LICENSE Add README and LICENSE to staging repos 2017-10-23 16:39:02 +05:30
OWNERS Add enj as reviewer to OWNERS 2017-08-29 13:16:16 +00:00
README.md Fix Typo in apiserver README 2018-01-07 08:45:11 +05:30
code-of-conduct.md Add code-of-conduct.md to staging repos 2017-12-20 15:21:56 -05: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 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

  1. Directly modify any files under pkg in this repo. Those are driven from k8s.io/kubernetes/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.