Skip to content

Commit

Permalink
spec: add optional secrets to NodeGetVolumeStatsRequest
Browse files Browse the repository at this point in the history
For BlockVolume type of volumes, there are very little stats that can be
gathered. The only reasonable metric on the Node that is available
without knowing the contents of the BlockVolume, is the Total capacity.

Different backend storage systems can thin-provision BlockVolumes.
Initially the Used storage will be low, and growing over time. This is
not detectable through standard Operating System APIs, but the backend
storage system can provide more acurate Available/Used stats through
expert APIs.

In order to allow the Node to retrieve advanced stats from the backend
storage system, the secrets that are used for staging the volume can be
provided.
  • Loading branch information
nixpanic committed May 3, 2021
1 parent da58351 commit f2d012b
Show file tree
Hide file tree
Showing 3 changed files with 262 additions and 234 deletions.
7 changes: 7 additions & 0 deletions csi.proto
Original file line number Diff line number Diff line change
Expand Up @@ -1395,6 +1395,13 @@ message NodeGetVolumeStatsRequest {
// system/filesystem, but, at a minimum, SP MUST accept a max path
// length of at least 128 bytes.
string staging_target_path = 3;

// Secrets that the plugin can use to request additional statistics
// from the backend storage system.
// This field is OPTIONAL. Refer to the `Secrets Requirements`
// section on how to use this field.
map<string, string> secrets = 4
[(csi_secret) = true, (alpha_field) = true];
}

message NodeGetVolumeStatsResponse {
Expand Down
Loading

0 comments on commit f2d012b

Please sign in to comment.