1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-06 16:06:56 +00:00
kyverno/vendor/k8s.io/cloud-provider
2019-10-23 23:19:53 -07:00
..
.github update vendor 2019-10-23 23:19:53 -07:00
features update vendor 2019-10-23 23:19:53 -07:00
Godeps update vendor 2019-10-23 23:19:53 -07:00
node/helpers update vendor 2019-10-23 23:19:53 -07:00
service/helpers update vendor 2019-10-23 23:19:53 -07:00
volume update vendor 2019-10-23 23:19:53 -07:00
cloud.go update vendor 2019-10-23 23:19:53 -07:00
code-of-conduct.md update vendor 2019-10-23 23:19:53 -07:00
CONTRIBUTING.md update vendor 2019-10-23 23:19:53 -07:00
doc.go update vendor 2019-10-23 23:19:53 -07:00
LICENSE update vendor 2019-10-23 23:19:53 -07:00
OWNERS update vendor 2019-10-23 23:19:53 -07:00
plugins.go update vendor 2019-10-23 23:19:53 -07:00
README.md update vendor 2019-10-23 23:19:53 -07:00
SECURITY_CONTACTS update vendor 2019-10-23 23:19:53 -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.