k3s/vendor/k8s.io/cloud-provider
Darren Shepherd 53ed13bf29 Update vendor
2020-04-18 23:59:08 -07:00
..
api Update vendor 2020-04-18 23:59:08 -07:00
node/helpers Update vendor 2020-04-18 23:59:08 -07:00
service/helpers Update vendor 2020-04-18 23:59:08 -07:00
volume Update vendor 2020-04-18 23:59:08 -07:00
BUILD Update vendor 2020-04-18 23:59:08 -07:00
cloud.go Update k8s to v1.17.3 2020-02-13 17:18:16 -07:00
code-of-conduct.md Update vendor 2019-08-30 23:08:05 -07:00
CONTRIBUTING.md Update vendor 2019-08-30 23:08:05 -07:00
doc.go Update vendor 2019-08-30 23:08:05 -07:00
go.mod Update vendor 2020-04-18 23:59:08 -07:00
go.sum Update vendor 2020-04-18 23:59:08 -07:00
LICENSE Update vendor 2019-08-30 23:08:05 -07:00
OWNERS Update vendor for k8s 1.17.0 2019-12-15 23:28:25 -07:00
plugins.go Update vendor 2019-09-27 16:54:32 -07:00
README.md Update vendor 2019-08-30 23:08:05 -07:00
SECURITY_CONTACTS Update vendor 2019-09-27 16:54:32 -07:00

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

  1. Add an cloud provider specific code to this repo.
  2. 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.
  3. Make interface changes without first discussing them with sig-cloudprovider.