-
Notifications
You must be signed in to change notification settings - Fork 275
C-WCOW: SecurityPolicy and sidecar fixes #2527
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Mahati Chamarthy <[email protected]>
Signed-off-by: Mahati Chamarthy <[email protected]>
0e7cadb to
95ea954
Compare
|
@msscotb Can this get a reviewer assigned please? |
| if isInitExec { | ||
| // if this is an exec of Container command line, then it's already enforced | ||
| // during container creation, hence skip it here | ||
| c.commandLineExec = true |
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.
is this basically "init process started" indicator? or rather "init process start attempted"
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.
also, is the assumption that no out of order exec requests will come?
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.
Requests are handled sequentially by gcs-sidecar. Also, isInitExec is a misnomer as it has nothing to do with init, I have changed the variable name. This is specifically to differentiate the exec at start container vs other exec processes.
Signed-off-by: Mahati Chamarthy <[email protected]>
95ea954 to
d7e2efe
Compare
Uh oh!
There was an error while loading. Please reload this page.