PacketCapture

A Packet Capture resource (PacketCapture) represents captured live traffic for debugging microservices and application interaction inside a Kubernetes cluster.

Calico Cloud supports selecting one or multiple WorkloadEndpoints resources as described in the Packet Capture guide.

For kubectl commands, the following case-insensitive aliases may be used to specify the resource type on the CLI: packetcapture,packetcaptures, packetcapture.projectcalico.org, packetcaptures.projectcalico.org as well as abbreviations such as packetcapture.p and packetcaptures.p.

Sample YAML

apiVersion: projectcalico.org/v3
kind: PacketCapture
metadata:
  name: sample-capture
  namespace: sample-namespace
spec:
  selector: k8s-app == "sample-app"
  filters:
    - protocol: TCP
      ports:
        - 80

apiVersion: projectcalico.org/v3
kind: PacketCapture
metadata:
  name: sample-capture
  namespace: sample-namespace
spec:
  selector: all()
  startTime: '2021-08-26T12:00:00Z'
  endTime: '2021-08-26T12:30:00Z'

Packet capture definition

Metadata

Field	Description	Accepted Values	Schema	Default
name	The name of the packet capture. Required.	Alphanumeric string with optional ., _, or -.	string
namespace	Namespace provides an additional qualification to a resource name.		string	"default"

Spec

Field	Description	Accepted Values	Schema	Default
selector	Selects the endpoints to which this packet capture applies.		selector
filters	The ordered set of filters applied to traffic captured from an interface.		filters
startTime	Defines the start time from which this PacketCapture will start capturing packets.	Date in RFC 3339 format	startTime
endTime	Defines the end time at which this PacketCapture will stop capturing packets.	Date in RFC 3339 format	endTime

Selector

A label selector is an expression which either matches or does not match a resource based on its labels.

Calico Cloud label selectors support a number of operators, which can be combined into larger expressions using the boolean operators and parentheses.

Expression	Meaning
Logical operators
( <expression> )	Matches if and only if <expression> matches. (Parentheses are used for grouping expressions.)
! <expression>	Matches if and only if <expression> does not match. Tip: ! is a special character at the start of a YAML string, if you need to use ! at the start of a YAML string, enclose the string in quotes.
<expression 1> && <expression 2>	"And": matches if and only if both <expression 1>, and, <expression 2> matches
<expression 1> || <expression 2>	"Or": matches if and only if either <expression 1>, or, <expression 2> matches.
Match operators
all()	Match all in-scope resources. To match no resources, combine this operator with ! to form !all().
global()	Match all non-namespaced resources. Useful in a namespaceSelector to select global resources such as global network sets.
k == 'v'	Matches resources with the label 'k' and value 'v'.
k != 'v'	Matches resources without label 'k' or with label 'k' and value not equal to v
has(k)	Matches resources with label 'k', independent of value. To match pods that do not have label k, combine this operator with ! to form !has(k)
k in { 'v1', 'v2' }	Matches resources with label 'k' and value in the given set
k not in { 'v1', 'v2' }	Matches resources without label 'k' or with label 'k' and value not in the given set
k contains 's'	Matches resources with label 'k' and value containing the substring 's'
k starts with 's'	Matches resources with label 'k' and value starting with the substring 's'
k ends with 's'	Matches resources with label 'k' and value ending with the substring 's'

Operators have the following precedence:

• Highest: all the match operators
• Parentheses ( ... )
• Negation with !
• Conjunction with &&
• Lowest: Disjunction with ||

For example, the expression

! has(my-label) || my-label starts with 'prod' && role in {'frontend','business'}

Would be "bracketed" like this:

((!(has(my-label)) || ((my-label starts with 'prod') && (role in {'frontend','business'}))

It would match:

• Any resource that did not have label "my-label".
• Any resource that both:
  • Has a value for my-label that starts with "prod", and,
  • Has a role label with value either "frontend", or "business".

Filters

Field	Description	Accepted Values	Schema	Default
protocol	Positive protocol match.	TCP, UDP, ICMP, ICMPv6, SCTP, UDPLite, 1-255	string | integer
ports	Positive match on the specified ports		list of ports

Calico Cloud supports the following syntax for expressing ports.

Syntax	Example	Description
int	80	The exact (numeric) port specified
start:end	6040:6050	All (numeric) ports within the range start ≤ x ≤ end

An individual numeric port may be specified as a YAML/JSON integer. A port range must be represented as a string. Named ports are not supported by PacketCapture. Multiple ports can be defined to filter traffic. All specified ports or port ranges concatenated using the logical operator "OR".

For example, this would be a valid list of ports:

ports: [8080, '1234:5678']

Multiple filter rules can be defined to filter traffic. All rules are concatenated using the logical operator "OR". For example, filtering both TCP or UDP traffic will be defined as:

filters:
  - protocol: TCP
  - protocol: UDP

Within a single filter rule, protocol and list of valid ports will be concatenated using the logical operator "AND".

For example, filtering TCP traffic and traffic for port 80 will be defined as:

filters:
  - protocol: TCP
    ports: [80]

StartTime

Defines the start time from which this PacketCapture will start capturing packets in RFC 3339 format. If omitted or the value is in the past, the capture will start immediately. If the value is changed to a future time, capture will stop immediately and restart at that time.

startTime: '2021-08-26T12:00:00Z'

EndTime

Defines the end time from which this PacketCapture will stop capturing packets in RFC 3339 format. If omitted the capture will continue indefinitely. If the value is changed to the past, capture will stop immediately.

endTime: '2021-08-26T12:30:00Z'

Status

PacketCaptureStatus lists the current state of a PacketCapture and its generated capture files.

Field	Description
files	It describes the location of the packet capture files that is identified via a node, its directory and the file names generated.

Files

Field	Description
directory	The path inside the calico-node container for the generated files.
fileNames	The name of the generated file for a PacketCapture ordered alphanumerically. The active packet capture file will be identified using the following schema: {<workload-endpoint-name}\_{<host-network-interface>}.pcap. Rotated capture files name will contain an index matching the rotation timestamp.
node	The hostname of the Kubernetes node the files are located on.
state	Determines whether a PacketCapture is capturing traffic from any interface attached to the current node. Possible values include: Capturing, Scheduled, Finished, Error, WaitingForTraffic