Pods and containers
Chronosphere Telemetry Pipeline uses pods (opens in a new tab) and containers (opens in a new tab) to manage different components of Telemetry Pipeline.
Pods
Use the information in this section to perform operations related to pods.
Specify pipeline pod termination time
You can specify how long Kubernetes should wait before forcefully terminating the
pod that runs a pipeline. To do so, add the following flag to a create pipeline
or update pipeline
command:
calyptia {create|update} pipeline --termination-grace-period-seconds VALUE
Replace VALUE
with a non-negative integer, which represents a time in seconds.
If unspecified, the default value is 30
.
For more information, see the terminationGracePeriodSeconds
entry in the Kubernetes API documentation (opens in a new tab).
Containers
Use the information in this section to perform operations related to containers.
Configure container lifecycle
You can configure a pipeline container to execute certain actions in response to
lifecycle events. To do so, add the following flag to a create pipeline
or
update pipeline
command:
calyptia {create|update} pipeline --lifecycle JSON
Replace JSON
with a JSON object that contains your lifecycle settings. You can
also pass an empty JSON object ({}
) to remove any existing lifecycle settings.
For more information, see the Lifecycle
entry in the
Kubernetes API documentation (opens in a new tab).
View from-cloud
and to-cloud
container logs
Each Core Instance pod includes two containers that synchronize pipeline resources.
- The
from-cloud
container receives updates from the Telemetry Pipeline backend and pushes those updates to your Kubernetes cluster. - The
to-cloud
container sends information about changes within your cluster to the Telemetry Pipeline backend.
You can use the following kubectl command to view logs from each of these containers:
kubectl logs POD CONTAINER
Replace the following values:
POD
: The name of the Core Instance pod.CONTAINER
: Eitherfrom-cloud
orto-cloud
.