kubernetes
/
kubelet
mirror of https://github.com/kubernetes/kubelet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kubelet component configs
945 Commits 24 Branches 1,336 Tags 5 MiB
Go 100%
Go to file
Ben Luddy 263e7e6ff2 Update indirect dependencies with ./hack/update-vendor.sh. 
Implementing custom marshaling on several API types for CBOR makes the upstream CBOR library an
indirect dependency of several staging modules.

Kubernetes-commit: d7cccf3e792ad08d9ab2e7aac394f8e6ddcf3466
 		2024-05-17 13:02:26 -04:00
.github Add skeleton new repo files 2018-09-02 14:23:12 +03:00
config add no swap as the default option for swap 2024-01-12 14:42:51 -05:00
pkg DRA: remove support for v1alpha2 kubelet API 2024-04-10 14:50:46 +02:00
CONTRIBUTING.md Update deprecated links 2019-02-04 13:28:31 -05:00
LICENSE Add skeleton new repo files 2018-09-02 14:23:12 +03:00
OWNERS Check in OWNERS modified by update-yamlfmt.sh 2021-12-09 21:31:26 -05:00
README.md staging: add dummy commit to trigger gomod update (#106794) 2021-12-03 10:23:17 +00:00
SECURITY_CONTACTS Update SECURITY_CONTACTS with current PSC 2019-05-29 15:22:35 +05:30
code-of-conduct.md Add skeleton new repo files 2018-09-02 14:23:12 +03:00
doc.go Make package paths referenced by import boss valid 2021-09-28 13:06:39 -04:00
go.mod Update indirect dependencies with ./hack/update-vendor.sh. 2024-05-17 13:02:26 -04:00
go.sum Update indirect dependencies with ./hack/update-vendor.sh. 2024-05-17 13:02:26 -04:00

README.md

kubelet

Implements KEP 14 - Moving ComponentConfig API types to staging repos

This repo provides external, versioned ComponentConfig API types for configuring the kubelet. These external types can easily be vendored and used by any third-party tool writing Kubernetes ComponentConfig objects.

Compatibility

HEAD of this repo will match HEAD of k8s.io/apiserver, k8s.io/apimachinery, and k8s.io/client-go.

Where does it come from?

This repo is synced from https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/kubelet. Code changes are made in that location, merged into k8s.io/kubernetes and later synced here by a bot.