| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
instance dying abnormally (qdisc deletion is part of exit callback for
pod under monitoring, but if clovisor exits abnormally, qdisc would not
be deleted, which cause the restarted new clovisor pod unable to load
BPF code to the pods under monitoring)
Change-Id: I5620f34e7f05805e203d1cfda9a8f7a1d42fd4f5
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
1.) make clovisor work on GKE
2.) running more efficient correlation between k8s service, pods, and
service port name for the pod's container port
3.) add per session trace metrics on Clovisor's traces, including
request and response sizes, trace-id, request-id, and more HTTP header
fields
4.) improve eBPF code to account for TCP sessions which do not finish with
either FIN or RST flags
5.) tested with Clover sample app (the "SDC")
Change-Id: Ia1a6275caf31a63fb1288c93cea42b32a4606307
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
Change-Id: Ied0ef2ccd4eb95cace68826a1494e82f2c18d95c
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
Part of Clover's initial task (during project proposal) is to explore
cloud native network tracing tools. Clover the project proposes
Clovisor as a way for Clover to use the IOvisor
(https://www.iovisor.org/) to perform network tracing. This is the first
commit of this module
Please note that the BPF code used in this commit were only tested with
Linux kernel 4.14+ --- hence, if ubuntu is used, and one prefers LTS,
the requirement is 18.04+
A different patch will track the redis and k8s API server watcher code
Also, a design doc will be added in the future (TBD)
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
Change-Id: I30d9f9d474b8703097c470d39628e86bc788f9b6
|
Stephen Wong