Showing results for 
Show  only  | Search instead for 
Did you mean: 

Kubernetes(K8s) - Classic Full stack vs Cloud Native approach


Hi All,

Please help me to understand exact difference between Classic and Cloud Native approaches for K8S monitoring.

Classic FS - in this only  oneagent image gets downloaded.

Cloud Native FS -in this both Oneagent image and code modules images get downloaded, code modules image is maintained by CSI driver.


1. what is the advantage of having extra code modules image in Cloud Native FS ?

2. What is the exact disadvantage in Classic FS that was overcome by cloud Native FS?





DynaMight Guru
DynaMight Guru

Hello @Gogi 

Both deployment options have their own advantages and limitations. The Classic full-stack injection is the recommended approach. When it comes to security concerns then, Cloud-native full-stack injection can be the solution.

Note: Classic full-stack injection requires to write access from the OneAgent pod to the Kubernetes node filesystem to detect and inject into newly deployed containers.





Be also aware that in Classic full-stack you cannot not select specific namespaces or exlude specific namespaces to monitor, which you might be interessted to keep the Host Unit consumption low, therefore you may prefer to go with Cloud-native full-stack.


I have few queries With respect to Classic Vs CloudNative approach
1. Does ClassicFullstack ask for application process/pods restart whenever new worker nodes spin up?
2. Whether application process/pods restart is not required in CloudNative FullStack when new worker nodes spin up?

Classic FullStack - my understanding is suppose we have 2 nodes now and we do node rollover then 2 new nodes comes up, on new nodes oneAgent process will start as demon(before application process start) so once application process starts it will do injection and start monitoring it(without restart of appln pods)

please clarify my understanding is correct or not.