Library for writing a Kubernetes-style API server.
Go to file
zhouhaibing089 79f762de77 componentstatus: support client cert health check
etcd has support for client-cert-auth, which can be configured via the flag `--ca-file`,
when that is enabled, all the client requests must present with a client certificate,
however, the current component status check uses a single transport for all of the checks,
this is wrong, the checks should be different for each of different component, and make
each of them use different transport(tls configurations).

Kubernetes-commit: b1040171b68217dccb617de85defa4a5063c638b
2017-04-22 20:36:06 +00:00
Godeps sync: resync vendor folder 2017-04-21 20:36:18 +00:00
hack handle resetting godep.json for resync 2017-02-23 11:14:39 -05:00
pkg componentstatus: support client cert health check 2017-04-22 20:36:06 +00:00
plugin/pkg autogenerated 2017-04-15 20:35:23 +00:00
vendor sync: resync vendor folder 2017-04-19 20:36:16 +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 add readme and license 2017-01-13 13:29:55 -05:00
kubernetes-sha sync(k8s.io/kubernetes) ee86c18d9239b6bfc2657e1b9cca6c80fd49f103 2017-04-21 20:35:37 +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/kubernetes/cmd/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.