Class V1EmptyDirVolumeSource
java.lang.Object
io.kubernetes.client.openapi.models.V1EmptyDirVolumeSource
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen",
date="2024-04-23T13:45:09.091597Z[Etc/UTC]")
public class V1EmptyDirVolumeSource
extends Object
Represents an empty directory for a pod. Empty directory volumes support ownership management and SELinux relabeling.
-
Nested Class Summary
Nested Classes -
Field Summary
Fields -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionboolean
static V1EmptyDirVolumeSource
Create an instance of V1EmptyDirVolumeSource given an JSON stringmedium represents what type of storage medium should back this directory.Quantity is a fixed-point representation of a number.int
hashCode()
void
void
setSizeLimit
(Quantity sizeLimit) toJson()
Convert an instance of V1EmptyDirVolumeSource to an JSON stringtoString()
static void
validateJsonObject
(com.google.gson.JsonObject jsonObj) Validates the JSON Object and throws an exception if issues found
-
Field Details
-
SERIALIZED_NAME_MEDIUM
- See Also:
-
SERIALIZED_NAME_SIZE_LIMIT
- See Also:
-
openapiFields
-
openapiRequiredFields
-
-
Constructor Details
-
V1EmptyDirVolumeSource
public V1EmptyDirVolumeSource()
-
-
Method Details
-
medium
-
getMedium
medium represents what type of storage medium should back this directory. The default is \"\" which means to use the node's default medium. Must be an empty string (default) or Memory. More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir- Returns:
- medium
-
setMedium
-
sizeLimit
-
getSizeLimit
Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors. The serialization format is: ``` <quantity> ::= <signedNumber><suffix> (Note that <suffix> may be empty, from the \"\" case in <decimalSI>.) <digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= \"+\" | \"-\" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html) <decimalSI> ::= m | \"\" | k | M | G | T | P | E (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.) <decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber> ``` No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities. When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized. Before serializing, Quantity will be put in \"canonical form\". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that: - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible. The sign will be omitted unless the number is negative. Examples: - 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\" Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise. Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.) This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation.- Returns:
- sizeLimit
-
setSizeLimit
-
equals
-
hashCode
public int hashCode() -
toString
-
validateJsonObject
Validates the JSON Object and throws an exception if issues found- Parameters:
jsonObj
- JSON Object- Throws:
IOException
- if the JSON Object is invalid with respect to V1EmptyDirVolumeSource
-
fromJson
Create an instance of V1EmptyDirVolumeSource given an JSON string- Parameters:
jsonString
- JSON string- Returns:
- An instance of V1EmptyDirVolumeSource
- Throws:
IOException
- if the JSON string is invalid with respect to V1EmptyDirVolumeSource
-
toJson
Convert an instance of V1EmptyDirVolumeSource to an JSON string- Returns:
- JSON string
-