Kubernetes deployment settings
Because all Telemetry Pipeline installations are deployed on top of Kubernetes, you can use Pipeline CLI to manage different Kubernetes deployment settings.
Namespaces
When you install or upgrade
a Core Operator, use the
--kube-namespace flag to set its namespace. However, like other types of Kubernetes
CRDs, Core Operator CRDs don't support namespace scoping.
Tolerations and taints
Tolerations and taints (opens in a new tab) can help you take advantage of high-availability hardware by ensuring that your deployments spread evenly.
Tolerations and taints are managed at the Core Instance level, and are applied to all pipelines within that Core Instance. Setting tolerations or taints on individual pipelines is not supported.
Pipeline CLI lets you specify tolerations for new Core Instances. However, you can't use Pipeline CLI to add or modify tolerations for an existing Core Instance.
To specify tolerations for a new Core Instance, use the --tolerations flag:
calyptia create core_instance operator --name INSTANCE --tolerations STRINGReplace the following values:
INSTANCE: The name for your new Core Instance.STRING: The string that specifies your tolerations.
The string that specifies your tolerations must follow this syntax:
key1=operator:value1:effect,key2=operator:value2:effectYou can also leave certain sections of this string blank to omit certain
toleration parameters. For example, =Exists:: is a valid toleration string.
Annotations
Annotations (opens in a new tab) let you attach custom metadata to Telemetry Pipeline resources. These annotations won't affect Telemetry Pipeline's behavior.
Pipeline CLI lets you specify tolerations for new resources. However, you can't use Pipeline CLI to add or modify tolerations for an existing resource.
When you create a new resource, add the --annotations flag to your operation,
and include an annotations string.
The string that specifies your annotations must follow this syntax:
annotation1=value1,annotation2=value2