Skip to content
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.

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

Reference datapath metrics in feature and troubleshooting guides #20520

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion Documentation/network/kubernetes/kubeproxy-free.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1175,7 +1175,8 @@ Graceful Termination
Cilium's eBPF kube-proxy replacement supports graceful termination of service
endpoint pods. The feature requires at least Kubernetes version 1.20, and
the feature gate ``EndpointSliceTerminatingCondition`` needs to be enabled.
By default, the Cilium agent then detects such terminating Pod state. If needed,
By default, the Cilium agent then detects such terminating Pod events, and
increments the metric ``k8s_terminating_endpoints_events_total``. If needed,
the feature can be disabled with the configuration option ``enable-k8s-terminating-endpoint``.

The cilium agent feature flag can be probed by running ``cilium status`` command:
Expand Down
5 changes: 4 additions & 1 deletion Documentation/operations/troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -404,7 +404,10 @@ default. The default starting interval is 5 minutes. Alternatively, the value
for ``bpf-ct-global-any-max`` and ``bpf-ct-global-tcp-max`` can be increased.
Setting both of these options will be a trade-off of CPU for ``conntrack-gc-interval``, and for
``bpf-ct-global-any-max`` and ``bpf-ct-global-tcp-max`` the amount of memory
consumed.
consumed. You can track conntrack garbage collection related metrics such as
``datapath_conntrack_gc_runs_total`` and ``datapath_conntrack_gc_entries`` to
get visibility into garbage collection runs. Refer to :ref:`metrics` for more
details.

Enabling datapath debug messages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down