LauncherProfile
LauncherProfile custom resource schema.
The LauncherProfile CRD holds reusable Kubernetes and launcher realization policy. Nodes
reference profiles explicitly via launcherProfileRef.
With statusProbes.enabled, readiness first requires the nested Docker container to be running
and, when defined by the image, its Docker healthcheck to be healthy. A running image without a
healthcheck provides process-level readiness only; configure an image healthcheck or an explicit
TCP/SSH probe when application readiness matters. For grouped Nodes, generic readiness covers every
member, while TCP/SSH checks remain scoped to the primary Node.
LauncherProfile
SPEC
LauncherProfileSpec is the spec for a LauncherProfile resource.
-
Deployment holds launcher deployment settings.
-
ContainerlabDebug sets the containerlab --debug flag.
-
ContainerlabTimeout sets the containerlab --timeout flag.
-
ContainerlabVersion selects a custom containerlab version, downloaded by the launcher at startup in place of the one baked into the image. 0.78.0 is the floor: the Node spec vocabulary includes fields (i.e. privileged, tmpfs, security-opts) that older containerlab releases reject outright, so pinning further back makes those nodes fail to deploy.
-
ExtraEnv is a list of additional environment variables for the launcher container.
-
EnvVar represents an environment variable present in a Container.
-
Name of the environment variable. May consist of any printable ASCII characters except '='.
-
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 "".
-
Source for the environment variable's value. Cannot be used if value is not empty.
-
Selects a key of a ConfigMap.
-
The key to select.
-
Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
default: "" -
Specify whether the ConfigMap or its key must be defined
-
-
Selects a field of the pod: supports metadata.name, metadata.namespace,
metadata.labels['<KEY>'],metadata.annotations['<KEY>'], spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.-
Version of the schema the FieldPath is written in terms of, defaults to "v1".
-
Path of the field to select in the specified API version.
-
-
FileKeyRef selects a key of the env file. Requires the EnvFiles feature gate to be enabled.
-
The key within the env file. An invalid key will prevent the pod from starting. The keys defined within a source may consist of any printable ASCII characters except '='. During Alpha stage of the EnvFiles feature gate, the key size is limited to 128 characters.
-
Specify whether the file or its key must be defined. If the file or key does not exist, then the env var is not published. If optional is set to true and the specified key does not exist, the environment variable will not be set in the Pod's containers.
If optional is set to false and the specified key does not exist, an error will be returned during Pod creation.
default: false -
The path within the volume from which to select the file. Must be relative and may not contain the '..' path or start with '..'.
-
The name of the volume mount containing the env file.
-
-
Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
-
Container name: required for volumes, optional for env vars
-
Specifies the output format of the exposed resources, defaults to "1"
-
Required: resource to select
-
-
Selects a key of a secret in the pod's namespace
-
The key of the secret to select from. Must be a valid secret key.
-
Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
default: "" -
Specify whether the Secret or its key must be defined
-
-
-
-
-
LauncherImage selects the launcher image.
-
LauncherImagePullPolicy selects the launcher image pull policy.
enum: "IfNotPresent", "Always", "Never" -
LauncherLogLevel selects the launcher log level.
enum: "disabled", "critical", "warn", +2 more -
Persistence enables persistence of the containerlab working directory.
-
ClaimSize is the size of the PVC for this topology -- if not provided this defaults to 5Gi. If provided, the string value must be a valid kubernetes storage requests style string. Note the claim size cannot be made smaller once created, but it can be expanded. If you need to make the claim smaller you must delete the topology (or the node from the topology) and re-add it.
-
Enabled indicates if persistence of hte containerlab lab/working directory will be placed in a mounted PVC.
-
StorageClassName is the storage class to set in the PVC -- if not provided this will be left empty which will end up using your default storage class. Note that currently we assume you have (as default) or provide a dynamically provisionable storage class, hence no selector.
-
-
PrivilegedLauncher configures launcher containers as privileged.
-
-
Expose holds configurations relevant to how Nodes using this profile are exposed.
-
DisableAutoExpose disables automatic exposure of the default port list.
-
DisableExpose indicates if exposing Nodes via a Service should be disabled.
-
ExposeType configures the Service type used for exposing Nodes.
enum: "None", "ClusterIP", "Headless", "LoadBalancer" -
UseNodeMgmtIpv4Address assigns a Node's management IPv4 address as its LoadBalancerIP.
-
UseNodeMgmtIpv6Address assigns a Node's management IPv6 address as its LoadBalancerIP.
-
-
ImagePull holds configurations relevant to how launcher Pods handle pulling images.
-
DockerConfig names the Secret containing config.json.
-
DockerDaemonConfig names the Secret containing daemon.json.
-
InsecureRegistries is a slice of insecure registries to configure in launcher Pods.
-
PullSecrets provides Secrets to use when pulling images.
-
PullThroughOverride overrides the image pull-through mode.
enum: "auto", "always", "never"
-
-
Mgmt temporarily retains shared containerlab management network settings for Topology compatibility. Its final ownership is intentionally deferred.
-
ExternalAccess enables (or disables) external access to the management network.
-
IPv4Gw is the IPv4 gateway of the management network.
-
IPv4Range is the IPv4 range of the management network.
-
IPv4Subnet is the IPv4 subnet of the management network.
-
IPv6Gw is the IPv6 gateway of the management network.
-
IPv6Range is the IPv6 range of the management network.
-
IPv6Subnet is the IPv6 subnet of the management network.
-
MTU is the MTU of the management network.
-
Network is the name of the docker network to use for the management network.
-
-
Resources holds the Kubernetes resource requirements for launcher Pods.
-
Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.
This field depends on the DynamicResourceAllocation feature gate.
This field is immutable. It can only be set for containers.
-
ResourceClaim references one entry in PodSpec.ResourceClaims.
-
Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container.
-
Request is the name chosen for a request in the referenced claim. If empty, everything from the claim is made available, otherwise only the result of this request.
-
-
-
Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
-
Schema for additional map entries.
-
-
-
Scheduling holds launcher Pod scheduling settings.
-
Affinity sets the affinity rules that will be configured on all launcher pods using this scheduling policy. This supports node affinity, pod affinity, and pod anti-affinity.
-
Describes node affinity scheduling rules for the pod.
-
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node matches the corresponding matchExpressions; the node(s) with the highest sum are the most preferred.
-
An empty preferred scheduling term matches all objects with implicit weight 0 (i.e. it's a no-op). A null preferred scheduling term matches no objects (i.e. is also a no-op).
-
A node selector term, associated with the corresponding weight.
-
A list of node selector requirements by node's labels.
-
A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
The label key that the selector applies to.
-
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
-
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
-
-
-
A list of node selector requirements by node's fields.
-
A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
The label key that the selector applies to.
-
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
-
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
-
-
-
-
Weight associated with matching the corresponding nodeSelectorTerm, in the range 1-100.
format: int32
-
-
-
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to an update), the system may or may not try to eventually evict the pod from its node.
-
Required. A list of node selector terms. The terms are ORed.
-
A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.
-
A list of node selector requirements by node's labels.
-
A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
The label key that the selector applies to.
-
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
-
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
-
-
-
A list of node selector requirements by node's fields.
-
A node selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
The label key that the selector applies to.
-
Represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists, DoesNotExist. Gt, and Lt.
-
An array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. If the operator is Gt or Lt, the values array must have a single element, which will be interpreted as an integer. This array is replaced during a strategic merge patch.
-
-
-
-
-
-
-
Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).
-
The scheduler will prefer to schedule pods to nodes that satisfy the affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling affinity expressions, etc.), compute a sum by iterating through the elements of this field and adding "weight" to the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
-
The weights of all of the matched WeightedPodAffinityTerm fields are added per-node to find the most preferred node(s)
-
Required. A pod affinity term, associated with the corresponding weight.
-
A label query over a set of resources, in this case pods. If it's null, this PodAffinityTerm matches with no Pods.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey in (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. -
MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey notin (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. -
A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means "this pod's namespace". An empty selector ({}) matches all namespaces.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means "this pod's namespace".
-
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
-
-
weight associated with matching the corresponding podAffinityTerm, in the range 1-100.
format: int32
-
-
-
If the affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
-
Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key matches that of any node on which a pod of the set of pods is running
-
A label query over a set of resources, in this case pods. If it's null, this PodAffinityTerm matches with no Pods.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey in (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. -
MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey notin (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. -
A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means "this pod's namespace". An empty selector ({}) matches all namespaces.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means "this pod's namespace".
-
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
-
-
-
-
Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).
-
The scheduler will prefer to schedule pods to nodes that satisfy the anti-affinity expressions specified by this field, but it may choose a node that violates one or more of the expressions. The node that is most preferred is the one with the greatest sum of weights, i.e. for each node that meets all of the scheduling requirements (resource request, requiredDuringScheduling anti-affinity expressions, etc.), compute a sum by iterating through the elements of this field and subtracting "weight" from the sum if the node has pods which matches the corresponding podAffinityTerm; the node(s) with the highest sum are the most preferred.
-
The weights of all of the matched WeightedPodAffinityTerm fields are added per-node to find the most preferred node(s)
-
Required. A pod affinity term, associated with the corresponding weight.
-
A label query over a set of resources, in this case pods. If it's null, this PodAffinityTerm matches with no Pods.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey in (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. -
MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey notin (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. -
A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means "this pod's namespace". An empty selector ({}) matches all namespaces.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means "this pod's namespace".
-
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
-
-
weight associated with matching the corresponding podAffinityTerm, in the range 1-100.
format: int32
-
-
-
If the anti-affinity requirements specified by this field are not met at scheduling time, the pod will not be scheduled onto the node. If the anti-affinity requirements specified by this field cease to be met at some point during pod execution (e.g. due to a pod label update), the system may or may not try to eventually evict the pod from its node. When there are multiple elements, the lists of nodes corresponding to each podAffinityTerm are intersected, i.e. all terms must be satisfied.
-
Defines a set of pods (namely those matching the labelSelector relative to the given namespace(s)) that this pod should be co-located (affinity) or not co-located (anti-affinity) with, where co-located is defined as running on a node whose value of the label with key matches that of any node on which a pod of the set of pods is running
-
A label query over a set of resources, in this case pods. If it's null, this PodAffinityTerm matches with no Pods.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
MatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey in (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both matchLabelKeys and labelSelector. Also, matchLabelKeys cannot be set when labelSelector isn't set. -
MismatchLabelKeys is a set of pod label keys to select which pods will be taken into consideration. The keys are used to lookup values from the incoming pod labels, those key-value labels are merged with
labelSelectoraskey notin (value)to select the group of existing pods which pods will be taken into consideration for the incoming pod's pod (anti) affinity. Keys that don't exist in the incoming pod labels will be ignored. The default value is empty. The same key is forbidden to exist in both mismatchLabelKeys and labelSelector. Also, mismatchLabelKeys cannot be set when labelSelector isn't set. -
A label query over the set of namespaces that the term applies to. The term is applied to the union of the namespaces selected by this field and the ones listed in the namespaces field. null selector and null or empty namespaces list means "this pod's namespace". An empty selector ({}) matches all namespaces.
-
matchExpressions is a list of label selector requirements. The requirements are ANDed.
-
A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
-
key is the label key that the selector applies to.
-
operator represents a key's relationship to a set of values. Valid operators are In, NotIn, Exists and DoesNotExist.
-
values is an array of string values. If the operator is In or NotIn, the values array must be non-empty. If the operator is Exists or DoesNotExist, the values array must be empty. This array is replaced during a strategic merge patch.
-
-
-
-
namespaces specifies a static list of namespace names that the term applies to. The term is applied to the union of the namespaces listed in this field and the ones selected by namespaceSelector. null or empty namespaces list and null namespaceSelector means "this pod's namespace".
-
This pod should be co-located (affinity) or not co-located (anti-affinity) with the pods matching the labelSelector in the specified namespaces, where co-located is defined as running on a node whose value of the label with key topologyKey matches that of any node on which any of the selected pods is running. Empty topologyKey is not allowed.
-
-
-
-
-
Tolerations is a list of Tolerations that will be set on the launcher pod spec.
-
The pod this Toleration is attached to tolerates any taint that matches the triple <key,value,effect> using the matching operator .
-
Effect indicates the taint effect to match. Empty means match all taint effects. When specified, allowed values are NoSchedule, PreferNoSchedule and NoExecute.
-
Key is the taint key that the toleration applies to. Empty means match all taint keys. If the key is empty, operator must be Exists; this combination means to match all values and all keys.
-
Operator represents a key's relationship to the value. Valid operators are Exists, Equal, Lt, and Gt. Defaults to Equal. Exists is equivalent to wildcard for value, so that a pod can tolerate all taints of a particular category. Lt and Gt perform numeric comparisons (requires feature gate TaintTolerationComparisonOperators).
-
TolerationSeconds represents the period of time the toleration (which must be of effect NoExecute, otherwise this field is ignored) tolerates the taint. By default, it is not set, which means tolerate the taint forever (do not evict). Zero and negative values will be treated as 0 (evict immediately) by the system.
format: int64 -
Value is the taint value the toleration matches to. If the operator is Exists, the value should be empty, otherwise just a regular string.
-
-
-
-
StatusProbes holds the configurations used to check and report Node status.
-
Enabled sets the status probes to enabled (or obviously disabled). A Node that has previously started but later fails its readiness check remains running and is reported not ready. A Node that never passes its startup check is restarted after its startup allowance expires.
default: true -
ExcludedNodes is a set of nodes to be excluded from status probe checking. It may be desirable to exclude some node(s) from status checking due to them not having an easy way for clabernetes to check the state of the node. The node names here should match the name of the nodes in the containerlab sub-topology.
-
NodeProbeConfigurations is a map of node specific probe configurations -- if you only need a simple ssh or tcp connect style setup that works on all node types in the topology you can ignore this and just configure ProbeConfiguration.
-
ProbeConfiguration holds optional application-specific probes for a (containerlab) node in a Topology. If both styles are configured, both and the generic nested-container probe must succeed in order to report healthy.
-
StartupSeconds is the total amount of seconds to allow for the node to start. This defaults to roughly 15 minutes to account for slow-to-boot nodes. The allowance must include time for c9s to pull the image, load it into Docker on the launcher, and boot the node. A larger value does not delay fast nodes because the readiness probe takes over as soon as startup succeeds.
-
TCPProbeConfiguration defines a TCP probe.
-
Port defines the port to try to open a TCP connection to. When using TCP probe setup this connection happens inside the launcher rather than the "normal" k8s style probes. This style probe behaves like a k8s style probe though in that it is "successful" whenever a TCP connection to this port can be opened successfully.
-
-
-
ProbeConfiguration is the default probe configuration for the Topology.
-
StartupSeconds is the total amount of seconds to allow for the node to start. This defaults to roughly 15 minutes to account for slow-to-boot nodes. The allowance must include time for c9s to pull the image, load it into Docker on the launcher, and boot the node. A larger value does not delay fast nodes because the readiness probe takes over as soon as startup succeeds.
-
TCPProbeConfiguration defines a TCP probe.
-
Port defines the port to try to open a TCP connection to. When using TCP probe setup this connection happens inside the launcher rather than the "normal" k8s style probes. This style probe behaves like a k8s style probe though in that it is "successful" whenever a TCP connection to this port can be opened successfully.
-
-
STATUS
LauncherProfileStatus is the status for a LauncherProfile resource.