You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **Note:** This feature is currently under experimental development.
4
+
5
+
## Overview
6
+
7
+
The `TraceConfiguration` CustomResourceDefinition (CRD) introduces a custom resource named `TraceConfiguration` that enables users to configure packet traces in a Kubernetes cluster. Packet traces can be tailored to specific use cases, offering the flexibility to capture detailed network data for debugging or continuous streaming of traces for security purposes.
8
+
9
+
## CRD Specification
10
+
11
+
The full specification for the `MetricsConfiguration` CRD can be found in the [TraceConfiguration CRD](https://github.com/microsoft/retina/blob/main/deploy/manifests/controller/helm/retina/crds/retina.sh_tracesconfigurations.yaml) file.
12
+
13
+
The `TraceConfiguration` CRD is defined with the following specifications:
14
+
15
+
-**API Group:** retina.sh
16
+
-**API Version:** v1alpha1
17
+
-**Kind:** TraceConfiguration
18
+
-**Plural:** traceconfigurations
19
+
-**Singular:** traceconfiguration
20
+
-**Scope:** Namespaced
21
+
22
+
### Fields
23
+
24
+
-**spec.traceConfigurations:** Specifies the detailed configuration options for packet tracing. It includes the following properties:
25
+
-`captureLevel`: Specifies the capture level, which can be set to `allPackets` or `firstPacket` (default).
26
+
-`includeLayer7Data`: Indicates whether layer 7 data (HTTP, DNS, TLS) should be included in the trace (default is `false`).
27
+
-`from`: Specifies the source entities from which packets will be captured, including IP blocks, namespaces, pods, and more.
28
+
-`to`: Specifies the destination entities to which packets will be captured, including IP blocks, services, and more.
29
+
-`ports`: Specifies the ports and protocols to capture packets for.
30
+
31
+
-**spec.tracePoints:** Specifies the types of trace points to capture, such as pod, nodeToPod, and nodeToNetwork.
32
+
33
+
-**spec.outputConfiguration:** Specifies the output destination and connection configuration for trace data. It includes the following properties:
34
+
-`destination`: Specifies the destination for trace data, which can be `stdout`, `azuretable`, `loganalytics`, or `opentelemetry`.
0 commit comments