Library for writing a Kubernetes-style API server.
Go to file
Kevin 41430fda7c use core client with explicit version globally
Kubernetes-commit: 4c8539cece2f0a6e6974b30d00c7341e10320bc5
2017-10-25 23:54:32 +08:00
Godeps Merge pull request #54513 from deads2k/admission-09-move 2017-10-27 08:53:22 +00:00
hack handle resetting godep.json for resync 2017-02-23 11:14:39 -05:00
pkg use core client with explicit version globally 2017-10-25 23:54:32 +08:00
plugin/pkg update BUILD files 2017-10-12 13:52:10 -07:00
vendor Merge pull request #52717 from FengyunPan/remove-LbassV1 2017-10-26 12:22:00 +00:00
.import-restrictions move pkg/auth/user to staging 2017-01-13 13:38:43 -05:00
LICENSE Remove README and LICENSE 2017-10-23 17:17:26 +05:30
OWNERS Add enj as reviewer to OWNERS 2017-08-29 13:16:16 +00:00
README.md Remove README and LICENSE 2017-10-23 17:17:26 +05:30

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/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.