v0.11.0: HTTP details on links where Cilium parses L7
Requests, response classes, p50/p95 latency and the busiest paths per link, from Hubble L7 flows (method, path, status, latency only; headers are never requested). The two inner legs of a proxied connection (Envoy -> pod, and the pod's answers to the node on an ephemeral port) are no longer counted as links. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
c50020e420
commit
4c5eb288cb
@@ -1,3 +1,8 @@
|
||||
v0.11.0:
|
||||
features:
|
||||
- "HTTP details where Cilium parses L7 (a CiliumNetworkPolicy with an http rule on the port): requests, responses by class, p50 and p95 latency and the ten busiest paths on the link, IDs in paths grouped as :id. Links with 5xx responses are drawn in the warning colour. Headers are never requested from Hubble. The docs have an example policy that turns this on for one service without restricting it."
|
||||
fixes:
|
||||
- "Traffic through the L7 proxy is counted once: Envoy's own connection to the pod no longer shows as a link from world, and the pod's answers to Envoy no longer add one link to the node per request. A pod that reached itself through its own Service is not shown as a link from world either."
|
||||
v0.10.0:
|
||||
features:
|
||||
- "Per-user visibility (auth.visibility: ViewerRBAC, the default): each viewer sees the namespaces where their own RBAC lets them list pods, or the whole cluster if they can list pods everywhere. Logs also need get pods/log, node cards list nodes; traffic peers in hidden namespaces are shown as hidden. Checked with SelfSubjectAccessReviews as the viewer, cached for a minute. auth.visibility: Everything keeps the previous behaviour."
|
||||
|
||||
Reference in New Issue
Block a user