9451: exlude Calico's special devices from dataIfaceRegex
Original PR Body below
It is confusing when users edit the regex what extra needs to be included. Now the user can focus on the true interfaces and forget about the once that calico uses for its own functionality.
Description
Related issues/PRs
Todos
[ ] Tests
[ ] Documentation
[ ] Release note
Release Note
ebpf: calico special interfaces excluded from dataIfaceRegex
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.
docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.
Every PR needs one release-note-* label.
release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.
Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.
Cherry pick of #9451 on release-v3.29.
9451: exlude Calico's special devices from dataIfaceRegex
Original PR Body below
It is confusing when users edit the regex what extra needs to be included. Now the user can focus on the true interfaces and forget about the once that calico uses for its own functionality.
Description
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.