Changes to accommodate client-go changes and kube vendor update

to v1.18.0

Signed-off-by: Humble Chirammal <hchiramm@redhat.com>

vendor/k8s.io/api/storage/v1/generated.proto

@@ -29,6 +29,97 @@ import "k8s.io/apimachinery/pkg/runtime/schema/generated.proto";
 // Package-wide variables from generator "generated".
 option go_package = "v1";
 
+// CSIDriver captures information about a Container Storage Interface (CSI)
+// volume driver deployed on the cluster.
+// Kubernetes attach detach controller uses this object to determine whether attach is required.
+// Kubelet uses this object to determine whether pod information needs to be passed on mount.
+// CSIDriver objects are non-namespaced.
+message CSIDriver {
+  // Standard object metadata.
+  // metadata.Name indicates the name of the CSI driver that this object
+  // refers to; it MUST be the same name returned by the CSI GetPluginName()
+  // call for that driver.
+  // The driver name must be 63 characters or less, beginning and ending with
+  // an alphanumeric character ([a-z0-9A-Z]) with dashes (-), dots (.), and
+  // alphanumerics between.
+  // More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  optional k8s.io.apimachinery.pkg.apis.meta.v1.ObjectMeta metadata = 1;
+
+  // Specification of the CSI Driver.
+  optional CSIDriverSpec spec = 2;
+}
+
+// CSIDriverList is a collection of CSIDriver objects.
+message CSIDriverList {
+  // Standard list metadata
+  // More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+  // +optional
+  optional k8s.io.apimachinery.pkg.apis.meta.v1.ListMeta metadata = 1;
+
+  // items is the list of CSIDriver
+  repeated CSIDriver items = 2;
+}
+
+// CSIDriverSpec is the specification of a CSIDriver.
+message CSIDriverSpec {
+  // attachRequired indicates this CSI volume driver requires an attach
+  // operation (because it implements the CSI ControllerPublishVolume()
+  // method), and that the Kubernetes attach detach controller should call
+  // the attach volume interface which checks the volumeattachment status
+  // and waits until the volume is attached before proceeding to mounting.
+  // The CSI external-attacher coordinates with CSI volume driver and updates
+  // the volumeattachment status when the attach operation is complete.
+  // If the CSIDriverRegistry feature gate is enabled and the value is
+  // specified to false, the attach operation will be skipped.
+  // Otherwise the attach operation will be called.
+  // +optional
+  optional bool attachRequired = 1;
+
+  // If set to true, podInfoOnMount indicates this CSI volume driver
+  // requires additional pod information (like podName, podUID, etc.) during
+  // mount operations.
+  // If set to false, pod information will not be passed on mount.
+  // Default is false.
+  // The CSI driver specifies podInfoOnMount as part of driver deployment.
+  // If true, Kubelet will pass pod information as VolumeContext in the CSI
+  // NodePublishVolume() calls.
+  // The CSI driver is responsible for parsing and validating the information
+  // passed in as VolumeContext.
+  // The following VolumeConext will be passed if podInfoOnMount is set to true.
+  // This list might grow, but the prefix will be used.
+  // "csi.storage.k8s.io/pod.name": pod.Name
+  // "csi.storage.k8s.io/pod.namespace": pod.Namespace
+  // "csi.storage.k8s.io/pod.uid": string(pod.UID)
+  // "csi.storage.k8s.io/ephemeral": "true" iff the volume is an ephemeral inline volume
+  //                                 defined by a CSIVolumeSource, otherwise "false"
+  //
+  // "csi.storage.k8s.io/ephemeral" is a new feature in Kubernetes 1.16. It is only
+  // required for drivers which support both the "Persistent" and "Ephemeral" VolumeLifecycleMode.
+  // Other drivers can leave pod info disabled and/or ignore this field.
+  // As Kubernetes 1.15 doesn't support this field, drivers can only support one mode when
+  // deployed on such a cluster and the deployment determines which mode that is, for example
+  // via a command line parameter of the driver.
+  // +optional
+  optional bool podInfoOnMount = 2;
+
+  // volumeLifecycleModes defines what kind of volumes this CSI volume driver supports.
+  // The default if the list is empty is "Persistent", which is the usage
+  // defined by the CSI specification and implemented in Kubernetes via the usual
+  // PV/PVC mechanism.
+  // The other mode is "Ephemeral". In this mode, volumes are defined inline
+  // inside the pod spec with CSIVolumeSource and their lifecycle is tied to
+  // the lifecycle of that pod. A driver has to be aware of this
+  // because it is only going to get a NodePublishVolume call for such a volume.
+  // For more information about implementing this mode, see
+  // https://kubernetes-csi.github.io/docs/ephemeral-local-volumes.html
+  // A driver can support one or more of these modes and
+  // more modes may be added in the future.
+  // This field is beta.
+  // +optional
+  // +listType=set
+  repeated string volumeLifecycleModes = 3;
+}
+
 // CSINode holds information about all CSI drivers installed on a node.
 // CSI drivers do not need to create the CSINode object directly. As long as
 // they use the node-driver-registrar sidecar container, the kubelet will