-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding smoke tests #653
adding smoke tests #653
Conversation
didn't understood the problem here, working fine locally. here ig the |
kubearmor/kubearmor-client#241 (comment) i opened an issue on kubearmor-client, ig it will ease out things here. after handling that we'll no longer required to handle policies from stdout and also the port-forward instruction will not be there to mess the json encoding. |
@rksharma95 now i'm getting the same error locally, seems like |
@nyrahul can you run thi pr locally and please confirm, are you getting an error? |
@rksharma95 , can you please check this? Thanks |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
4f735e3
to
76563ce
Compare
@rksharma95 @nyrahul please review the pr |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@nyrahul I tried to reduce the sleep time to 10 sec and also added the Also the test case for Network policy also checks for protocol type and port no., should we not check them because sometimes it passes and sometimes not. Basically the policcy keeps changing the protocol and port no. |
|
|
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@nyrahul while using sleep time 10 secs |
Ok i see, in general, the discovery-engine might require to observe at least for 10 seconds before it can discover the policy. |
Please point to specifics. What do you see changing? |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@rksharma95 can you please check why go-sec is failing, also @rksharma95 @nyrahul please review the pr |
@Prateeknandle PTAL https://www.joeshaw.org/dont-defer-close-on-writable-files/ ig it might help with deferring close() issues. |
@Prateeknandle PTAL kubearmor/KubeArmor#1098 for gosec issues. |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@rksharma95 @nyrahul now you can review the pr |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@seswarrajan here is the network policy we are getting after 300 seconds so the policy we are getting should be considered final, do you think this is a valid policy and test cases should be molded acc to this? policy have no protocal mentioned with port and port is also not 3306. |
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
Signed-off-by: Prateeknandle <prateeknandle@gmail.com>
@PrimalPimmy @rksharma95 can you please review the pr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Prateeknandle prateeknandle@gmail.com
opened new pr, old one is closed without merging, i blundered it during rebase.