f87d06ed85
Several packages are only used while running the e2e suite. These packages are less important to update, as the they can not influence the final executable that is part of the Ceph-CSI container-image. By moving these dependencies out of the main Ceph-CSI go.mod, it is easier to identify if a reported CVE affects Ceph-CSI, or only the testing (like most of the Kubernetes CVEs). Signed-off-by: Niels de Vos <ndevos@ibm.com> |
||
|---|---|---|
| .. | ||
| app/config | ||
| config | ||
| controllers | ||
| names | ||
| options | ||
| volume | ||
| cloud.go | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| 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.