mutation webhook

[achrefbensaad]

Work related to this issue

[achrefbensaad]

// TODO: reset all versions to v1 before releasing.

[codecov-commenter]

Codecov Report

Merging #655 (ef9a5bf) into main (93794fe) will decrease coverage by 0.91%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #655      +/-   ##
==========================================
- Coverage   35.93%   35.02%   -0.92%     
==========================================
  Files          25       25              
  Lines        9018     8888     -130     
==========================================
- Hits         3241     3113     -128     
- Misses       5327     5331       +4     
+ Partials      450      444       -6     

Impacted Files	Coverage Δ
KubeArmor/core/kubeUpdate.go	43.07% <100.00%> (-0.62%)	⬇️
KubeArmor/feeder/feeder.go	46.19% <0.00%> (-9.05%)	⬇️
KubeArmor/core/k8sHandler.go	31.69% <0.00%> (-3.93%)	⬇️
KubeArmor/feeder/policyMatcher.go	36.33% <0.00%> (-1.03%)	⬇️
KubeArmor/enforcer/appArmorEnforcer.go	47.56% <0.00%> (-0.74%)	⬇️
KubeArmor/monitor/systemMonitor.go	47.51% <0.00%> (-0.56%)	⬇️
KubeArmor/enforcer/runtimeEnforcer.go	37.93% <0.00%> (+1.72%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93794fe...ef9a5bf. Read the comment docs.

[nam-jaehyun]

Here is my first feedback.

1. please clean up your update in ci-test.yml and latest-release.yml

2. please keep the logic in kubeUpdate.go

The overall behavior should be something like this.
KubeArmor itself does not add annotations if the admission controller already adds them.
However, in the case that the admission controller is not running (required annotations are not added), 
we need to have a backup plan to handle annotations.

Besides, I'll give you some feedback for KubeArmorAdmission soon.

[nam-jaehyun]

Here is my first feedback.

1. please clean up your update in ci-test.yml and latest-release.yml

2. please keep the logic in kubeUpdate.go

The overall behavior should be something like this.
KubeArmor itself does not add annotations if the admission controller already adds them.
However, in the case that the admission controller is not running (required annotations are not added), 
we need to have a backup plan to handle annotations.

Besides, I'll give you some feedback for KubeArmorAdmission soon.

[nam-jaehyun]

@achrefbensaad can you (1) rebase the code, (2) exclude the updates for CI and kubeUpdate.go, and (3) make it a single commit?

[achrefbensaad]

Hey @nam-jaehyun, I rebased(1) and squashed (3) the commits on top of main.

[nam-jaehyun]

Good to merge it