- 1.11.1 (latest)
 - 1.11.0
 - 1.10.1
 - 1.9.0
 - 1.8.0
 - 1.7.0
 - 1.6.1
 - 1.5.0
 - 1.4.0
 - 1.3.0
 - 1.2.0
 - 1.1.1
 - 1.0.0
 - 0.42.0
 - 0.41.0
 - 0.40.0
 - 0.39.0
 - 0.38.0
 - 0.37.0
 - 0.36.0
 - 0.35.0
 - 0.34.1
 - 0.33.1
 - 0.32.0
 - 0.31.0
 - 0.30.0
 - 0.29.0
 - 0.28.0
 - 0.27.0
 - 0.26.0
 - 0.25.0
 - 0.24.0
 - 0.23.0
 - 0.22.0
 - 0.21.1
 - 0.20.0
 - 0.19.0
 - 0.18.0
 - 0.17.0
 - 0.16.3
 - 0.15.0
 - 0.14.0
 - 0.13.0
 - 0.12.0
 - 0.11.0
 - 0.10.0
 - 0.9.1
 - 0.8.0
 - 0.7.3
 
Reference documentation and code samples for the Kubernetes Engine V1 API class Google::Cloud::Container::V1::LocalNvmeSsdBlockConfig.
LocalNvmeSsdBlockConfig contains configuration for using raw-block local NVMe SSDs
Inherits
- Object
 
Extended By
- Google::Protobuf::MessageExts::ClassMethods
 
Includes
- Google::Protobuf::MessageExts
 
Methods
#local_ssd_count
def local_ssd_count() -> ::Integer- 
        (::Integer) — 
Number of local NVMe SSDs to use. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information.
A zero (or unset) value has different meanings depending on machine type being used:
- For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage.
 - For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info.
 
 
#local_ssd_count=
def local_ssd_count=(value) -> ::Integer- 
        value (::Integer) — 
Number of local NVMe SSDs to use. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information.
A zero (or unset) value has different meanings depending on machine type being used:
- For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage.
 - For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info.
 
 
- 
        (::Integer) — 
Number of local NVMe SSDs to use. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information.
A zero (or unset) value has different meanings depending on machine type being used:
- For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage.
 - For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info.