Skip to content

Conversation

@tallclair
Copy link
Contributor

Change CloudInfo to use a registration pattern, making the dependencies on the cloud provider SDKs optional. The CloudProviders are registered in the main cadvisor binary, so for non-library usages there are no changes.

For Kubernetes, I verified that the info provided by CloudInfo is unused by removing it and confirming everything still builds: tallclair/kubernetes@9274b43 (the only reference in Kubernetes was in the cadvisor fake)

@tallclair
Copy link
Contributor Author

For kubernetes/kubernetes#69585

@tallclair
Copy link
Contributor Author

/retest

Copy link
Collaborator

@dashpole dashpole left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@dashpole
Copy link
Collaborator

dashpole commented Apr 4, 2019

This will mean that the cadvisor v1 machine info returned by the kubelet's /spec/ endpoint won't have this information anymore. From cAdvisor's perspective, this is fine, but we should at least add that to the release notes in kubernetes, assuming the loss of this information from that endpoint is desired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants