• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..15-Sep-2021-

.github/H15-Sep-2021-32

cli/H15-Sep-2021-2,4381,727

codec/H15-Sep-2021-4016

config/H15-Sep-2021-1,6481,000

configz/H15-Sep-2021-206118

featuregate/H15-Sep-2021-894686

logs/H15-Sep-2021-2,5041,819

metrics/H15-Sep-2021-7,0174,883

term/H15-Sep-2021-4017

traces/H15-Sep-2021-9053

version/H15-Sep-2021-22199

CONTRIBUTING.mdH A D15-Sep-2021750 84

LICENSEH A D15-Sep-202111.1 KiB203169

OWNERSH A D15-Sep-2021257 2119

README.mdH A D15-Sep-20211.4 KiB3522

SECURITY_CONTACTSH A D15-Sep-2021567 1917

code-of-conduct.mdH A D15-Sep-2021148 42

go.modH A D15-Sep-20211.4 KiB4237

go.sumH A D15-Sep-202167.2 KiB696695

README.md

1## component-base
2
3## Purpose
4
5Implement KEP 32: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cluster-lifecycle/wgs/783-component-base/README.md
6
7The proposal is essentially about refactoring the Kubernetes core package structure in a way that all core components may share common code around:
8 - ComponentConfig implementation
9 - flag and command handling
10 - HTTPS serving
11 - delegated authn/z
12 - logging.
13
14## Compatibility
15
16There are *NO compatibility guarantees* for this repository, yet.  It is in direct support of Kubernetes, so branches
17will track Kubernetes and be compatible with that repo.  As we more cleanly separate the layers, we will review the
18compatibility guarantee. We have a goal to make this easier to use in the future.
19
20
21## Where does it come from?
22
23This repository is synced from https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/component-base.
24Code changes are made in that location, merged into `k8s.io/kubernetes` and later synced here.
25
26## Things you should *NOT* do
27
28 1. Directly modify any files in this repo. Those are driven from `k8s.io/kubernetes/staging/src/k8s.io/component-base`.
29 2. Expect compatibility. This repo is changing quickly in direct support of Kubernetes.
30
31### OWNERS
32
33WG Component Standard is working on this refactoring process, which is happening incrementally, starting in the v1.14 cycle.
34SIG API Machinery and SIG Cluster Lifecycle owns the code.
35