control-service: Container read-only file system#1291
control-service: Container read-only file system#1291gabrielgeorgiev1 merged 40 commits intomainfrom
Conversation
To reduce the attack surface of jobs containers, jobs should run with the root file system set to read-only. However, this means that job pods cannot write to the file system, so we need to create an ephemeral file system that jobs can use instead. Testing done: TBD Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
|
This is setting root file system for the builder jobs. And it looks ok. What happens for the data jobs themselves ? Are you planning to do it? It make sense to me to be a separate PR but I just wondered because initially it seems we are changing the data job . |
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
|
Probably you are going to expose this option through the Helm chart in a separate PR, right? |
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
I don't follow. My understanding was that this will be configured through values.yml. |
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Yes, but now it is not possible, since this property is not exposed yet, right? |
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
for more information, see https://pre-commit.ci
Signed-off-by: Gabriel Georgiev <gageorgiev@vmware.com>
…re/versatile-data-kit into person/gageorgiev/ephemeral-storage
for more information, see https://pre-commit.ci
To reduce the attack surface of jobs containers, jobs
should run with the root file system set to read-only.
However, this means that job pods cannot write to the
file system, so we need to create an ephemeral file
system that jobs can use instead.
The test job contains one step with the following code:
Testing done: integration test
Signed-off-by: Gabriel Georgiev gageorgiev@vmware.com