78211b694b
client-go 1.20.6 has a fix for below CVE: This patch address this via updating client-go and other dependencies. CVE-2019-11250 : The MITRE CVE dictionary describes this issue as: The Kubernetes client-go library logs request headers at verbosity levels of 7 or higher. This can disclose credentials to unauthorized users via logs or command output. Kubernetes components (such as kube-apiserver) prior to v1.16.0, which make use of basic or bearer token authentication, and run at high verbosity levels, are affected. Ref# https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11250 Signed-off-by: Humble Chirammal <hchiramm@redhat.com> |
||
---|---|---|
.. | ||
volume | ||
cloud.go | ||
code-of-conduct.md | ||
CONTRIBUTING.md | ||
doc.go | ||
go.mod | ||
go.sum | ||
LICENSE | ||
OWNERS | ||
plugins.go | ||
ports.go | ||
README.md | ||
SECURITY_CONTACTS |
cloud-provider
This repository defines the cloud-provider interface and mechanism to initialize a cloud-provider implementation into Kubernetes. Currently multiple processes use this code although the intent is that it will eventually only be cloud controller manager.
Note: go-get or vendor this package as k8s.io/cloud-provider
.
Purpose
This library is a shared dependency for processes which need to be able to integrate with cloud-provider specific functionality.
Compatibility
Cloud Providers are expected to keep the HEAD of their implementations in sync with the HEAD of this repository.
Where does it come from?
cloud-provider
is synced from
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/cloud-provider.
Code changes are made in that location, merged into k8s.io/kubernetes and
later synced here.
Things you should NOT do
- Add an cloud provider specific code to this repo.
- Directly modify anything under vendor/k8s.io/cloud-provider in this repo. Those are driven from
k8s.io/kubernetes/staging/src/k8s.io/cloud-provider
. - Make interface changes without first discussing them with sig-cloudprovider.