71925d553e
Bumping the k8s.io dependencies to v0.26.7. The main intention is to update the client-go library dependency for kube 1.27+, where aggregated discovery is enabled. With client-go lower than v0.26.4 in some cases it is possible that the discovery response comes with the malformed response with nil GVK leading to Crash Loop Back Off state. Upstream kubernetes issue: https://github.com/kubernetes/kubernetes/pull/116603 Signed-off-by: karthik-us <ksubrahm@redhat.com> |
||
---|---|---|
.. | ||
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.