Skip to content

Fix typo in eBPF debug log section #2268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ctauchen merged 2 commits into from
Sep 10, 2025
Merged

Fix typo in eBPF debug log section #2268

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c71d7e
Fix typo in eBPF debug log section
alexh-tigera Sep 8, 2025
be0bbc8
Merge branch 'tigera:main' into alexh-ebpf-typo
alexh-tigera Sep 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 166 in calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-cloud/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 166, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 166 in calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-cloud_versioned_docs/version-21-2/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 166, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 166 in calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-cloud_versioned_docs/version-22-1/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 166, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 168 in calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-enterprise/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 168, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion ...-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 168 in calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.19-2/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 168, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion ...-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 168 in calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.20-2/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 168, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion ...-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 168 in calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.21-2/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 168, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion ...-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 168 in calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico-enterprise_versioned_docs/version-3.22-1/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 168, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because

Check failure on line 166 in calico/operations/ebpf/troubleshoot-ebpf.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Vale.Spelling] Did you really mean 'PICKLEVAR's'?

Raw Output:
{"message": "[Vale.Spelling] Did you really mean 'PICKLEVAR's'?", "location": {"path": "calico/operations/ebpf/troubleshoot-ebpf.mdx", "range": {"start": {"line": 166, "column": 1}}}, "severity": "ERROR"}
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico_versioned_docs/version-3.28/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU:

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico_versioned_docs/version-3.29/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU:

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
2 changes: 1 addition & 1 deletion calico_versioned_docs/version-3.30/operations/ebpf/troubleshoot-ebpf.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ If you notice `$[noderunning]` using high CPU:

## eBPF program debug logs

$[prodname]'s eBPF programs contain optional detailed debug logging. Although th logs can be very verbose (because
$[prodname]'s eBPF programs contain optional detailed debug logging. Although the logs can be very verbose (because
the programs will log every packet), they can be invaluable to diagnose eBPF program issues. To enable the log, set the
`bpfLogLevel` Felix configuration setting to `Debug`.

Expand Down
Loading