test

Signed-off-by: sadath-12 <[email protected]>

ebpf_doc.txt

@@ -0,0 +1,17 @@
+ebpf:
+
+we first get the system call on which we want to attach our work(function) that needs to be executed on the kernel
+and attach it through kprobe and also take support of kernel function again to retrieve the information about it 
+those info is stored in some file for example the print one stores in  /sys/kernel/debug/tracing/trace_pipe.
+but it becomes very tough when things multiply and scale so we eBPF maps
+
+There are different eBPF maps for different purposes (socket , network ... etc)
+
+ Typical uses
+include the following:
+• User space writing configuration information to be retrieved by an eBPF
+program
+• An eBPF program storing state, for later retrieval by another eBPF program (or a
+future run of the same program)
+• An eBPF program writing results or metrics into a map, for retrieval by the user
+space app that will present results

info.txt

@@ -43,4 +43,22 @@ understand tetracli code properly
 February 22 - March 18 - GSOC
 mid-January - LFX
 
-how different clients are configured
+how different clients are configured
+understand that processmanager
+
+
+understand these compos role in cilium -- 	ciliumClient,
+			v1.NewEndpoints(),
+			ipcache.New(),
+			fqdncache.New(),
+			servicecache.New(),
+
+decode their structs
+that events who is consuming just check from the eventschannel
+
+handleMonitorSocket( consumes monitor events via ciliumState --> see the role of ciliumState here and how after monitoring it stores those events
+
+
+pkg/watcher/crd/watcher.go will watch the crds and trigger
+
+how is tetragonExecute executed ?

pkg/grpc/process_manager.go

@@ -52,7 +52,7 @@ func NewProcessManager(
 		"enableProcessNs":   option.Config.EnableProcessNs,
 	}).Info("Starting process manager")
 	return pm, nil
-}
+} 
 
 // Notify implements Listener.Notify.
 func (pm *ProcessManager) Notify(event notify.Message) error {