Jing Xu c401b2331c Handle the CSI driver in VolumeSnapshotContent does not match case
In VolumeSnapshotContent, if the CSI driver does not match the plugin's,
the controller should skip this content instead of always processing it.
This PR also add a few tests related to snapshot and content static
binding.

During binding, if content specify its bound snapshot uid and it
does not match the snapshot's uid, the content object and also the
physical snapshot will be deleted. In this case, the controller will
treat the content as an orphan content because its snapshot object does
not exist (deleted) any more.
2018-09-20 15:21:18 -07:00
2018-07-31 10:41:32 -07:00
2018-08-30 21:32:24 +08:00
2018-07-11 10:48:54 -07:00
2018-07-12 09:56:28 -07:00
2018-09-01 18:32:19 +05:30
2018-07-31 10:41:32 -07:00
2018-07-09 10:05:08 +03:00
2018-07-31 20:30:18 -07:00
2018-08-06 13:41:52 -07:00
2018-09-01 18:32:19 +05:30
2018-08-08 13:58:38 -07:00

external-snapshotter

Sidecar container that watches Kubernetes Snapshot CRD objects and triggers CreateSnapshot/DeleteSnapshot against a CSI endpoint.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

Description
No description provided
Readme 74 MiB
Languages
Go 85.8%
Shell 11.1%
Makefile 1.6%
Python 1.4%