Class V1CSINodeDriver
CSINodeDriver holds information about the specification of one CSI driver
installed on a node
Inheritance
V1CSINodeDriver
Assembly: KubernetesClient.dll
Syntax
public record V1CSINodeDriver : IEquatable<V1CSINodeDriver>
Constructors
View Source
V1CSINodeDriver()
Declaration
View Source
V1CSINodeDriver(V1CSINodeDriver)
Declaration
protected V1CSINodeDriver(V1CSINodeDriver original)
Parameters
Properties
View Source
Allocatable
allocatable represents the volume resources of a node that are available for
scheduling. This field is beta.
Declaration
[JsonPropertyName("allocatable")]
public V1VolumeNodeResources Allocatable { get; set; }
Property Value
View Source
EqualityContract
Declaration
protected virtual Type EqualityContract { get; }
Property Value
View Source
Name
name represents the name of the CSI driver that this object refers to. This MUST
be the same name returned by the CSI GetPluginName() call for that driver.
Declaration
[JsonPropertyName("name")]
public string Name { get; set; }
Property Value
View Source
NodeID
nodeID of the node from the driver point of view. This field enables Kubernetes
to communicate with storage systems that do not share the same nomenclature for
nodes. For example, Kubernetes may refer to a given node as "node1", but the
storage system may refer to the same node as "nodeA". When Kubernetes issues a
command to the storage system to attach a volume to a specific node, it can use
this field to refer to the node name using the ID that the storage system will
understand, e.g. "nodeA" instead of "node1". This field is required.
Declaration
[JsonPropertyName("nodeID")]
public string NodeID { get; set; }
Property Value
View Source
TopologyKeys
topologyKeys is the list of keys supported by the driver. When a driver is
initialized on a cluster, it provides a set of topology keys that it understands
(e.g. "company.com/zone", "company.com/region"). When a driver is initialized on
a node, it provides the same topology keys along with values. Kubelet will
expose these topology keys as labels on its own node object. When Kubernetes
does topology aware provisioning, it can use this list to determine which labels
it should retrieve from the node object and pass back to the driver. It is
possible for different nodes to use different topology keys. This can be empty
if driver does not support topology.
Declaration
[JsonPropertyName("topologyKeys")]
public IList<string> TopologyKeys { get; set; }
Property Value
Methods
View Source
Equals(object?)
Declaration
public override bool Equals(object? obj)
Parameters
| Type |
Name |
Description |
| object |
obj |
|
Returns
Overrides
View Source
Equals(V1CSINodeDriver?)
Declaration
public virtual bool Equals(V1CSINodeDriver? other)
Parameters
Returns
View Source
GetHashCode()
Declaration
public override int GetHashCode()
Returns
Overrides
View Source
PrintMembers(StringBuilder)
Declaration
protected virtual bool PrintMembers(StringBuilder builder)
Parameters
Returns
View Source
ToString()
Declaration
public override string ToString()
Returns
Overrides
Operators
View Source
operator ==(V1CSINodeDriver?, V1CSINodeDriver?)
Declaration
public static bool operator ==(V1CSINodeDriver? left, V1CSINodeDriver? right)
Parameters
Returns
View Source
operator !=(V1CSINodeDriver?, V1CSINodeDriver?)
Declaration
public static bool operator !=(V1CSINodeDriver? left, V1CSINodeDriver? right)
Parameters
Returns
Implements