Skip to content


"EnvVar represents an environment variable present in a Container."



fn new

new(name, value)

new returns a new envVar of given name and value

fn fromFieldPath

fromFieldPath(name, fieldPath)

fromFieldPath creates a envVar from a field path

fn fromSecretRef

fromSecretRef(name, secretRefName, secretRefKey)

fromSecretRef creates a envVar from a secret reference

fn withName


"Name of the environment variable. Must be a C_IDENTIFIER."

fn withValue


"Variable references $(VAR_NAME) are expanded using the previously defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. \"$$(VAR_NAME)\" will produce the string literal \"$(VAR_NAME)\". Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to \"\"."

obj valueFrom

"EnvVarSource represents a source for the value of an EnvVar."

obj valueFrom.configMapKeyRef

"Selects a key from a ConfigMap."

fn valueFrom.configMapKeyRef.withKey


"The key to select."

fn valueFrom.configMapKeyRef.withName


"Name of the referent. More info:"

fn valueFrom.configMapKeyRef.withOptional


"Specify whether the ConfigMap or its key must be defined"

obj valueFrom.fieldRef

"ObjectFieldSelector selects an APIVersioned field of an object."

fn valueFrom.fieldRef.withApiVersion


"Version of the schema the FieldPath is written in terms of, defaults to \"v1\"."

fn valueFrom.fieldRef.withFieldPath


"Path of the field to select in the specified API version."

obj valueFrom.resourceFieldRef

"ResourceFieldSelector represents container resources (cpu, memory) and their output format"

fn valueFrom.resourceFieldRef.withContainerName


"Container name: required for volumes, optional for env vars"

fn valueFrom.resourceFieldRef.withDivisor


"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.\n\nThe serialization format is:\n\n<quantity> ::= <signedNumber><suffix>\n\n\t(Note that <suffix> may be empty, from the \"\" case in <decimalSI>.)\n\n<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\n\n\t(International System of units; See:\n\n<decimalSI> ::= m | \"\" | k | M | G | T | P | E\n\n\t(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)\n\n<decimalExponent> ::= \"e\" <signedNumber> | \"E\" <signedNumber>\n\nNo 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.\n\nWhen 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.\n\nBefore 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:\n\n- No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible.\n\nThe sign will be omitted unless the number is negative.\n\nExamples:\n\n- 1.5 will be serialized as \"1500m\" - 1.5Gi will be serialized as \"1536Mi\"\n\nNote that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise.\n\nNon-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.)\n\nThis 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."

fn valueFrom.resourceFieldRef.withResource


"Required: resource to select"

obj valueFrom.secretKeyRef

"SecretKeySelector selects a key of a Secret."

fn valueFrom.secretKeyRef.withKey


"The key of the secret to select from. Must be a valid secret key."

fn valueFrom.secretKeyRef.withName


"Name of the referent. More info:"

fn valueFrom.secretKeyRef.withOptional


"Specify whether the Secret or its key must be defined"