feat(cp-node): Add systemd mode support for imagescan installation #401
Conversation
PaveenV
force-pushed
the
cp-node
branch
2 times, most recently
from
097cbc6 to
21c1277
Compare
PaveenV
changed the title
There was a problem hiding this comment.
So with In Cluster Scan for VM.. We will be additionally deploying kubeshield agent?
There was a problem hiding this comment.
If yes... Can we perform a benchmarking on the max memory being utilised by the services ??
There was a problem hiding this comment.
No, we are not deploying the kubeshield agent; we are running the knoxctl command to discover and scan the image in the VM.
For this benchmarking, we scanned 214 container images.
Benchmarking results:
- Consumed 2min 24.569s CPU time.
- 81.7M memory peak.
- 42.1M memory swap peak.
| DiscoverAgent string = "accuknox-discover" | ||
| HardeningAgent string = "accuknox-hardening-agent" | ||
| RRA string = "accuknox-rra" | ||
| Kubeshield string = "accuknox-scanner" |
There was a problem hiding this comment.
Why added twice ? One in line 93 and other in line 99?
There was a problem hiding this comment.
addressed, please verify
| CPUWeight=50 | ||
| {{- end }} | ||
|
|
||
| OOMPolicy=stop |
There was a problem hiding this comment.
We are missing a dependency env here... We might be dependent on spire-agent if it is a control-plane right... Can we add the same here..
There was a problem hiding this comment.
Added spire agent in the wants and after in the systemd service file.
Signed-off-by: Paveen Kumar <paveenkumar@accuknox.com>
2 participants
Purpose of this PR?
Ticket: https://accu-knox.atlassian.net/browse/CNAPP-24231