Updating our base image to use OSS static distroless image instead of scratch. This image runs with a specific UID we can configure our podsecuritycontext with. This gives us explicit control over file and process ownership and allows us to safely mount a homedir/filesystem that can be used for caching and other purposes.
Fixes # (issue)
Feature # (details)
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s)?
[x] e2e
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
Description
Updating our base image to use OSS static distroless image instead of scratch. This image runs with a specific UID we can configure our podsecuritycontext with. This gives us explicit control over file and process ownership and allows us to safely mount a homedir/filesystem that can be used for caching and other purposes.
Fixes # (issue) Feature # (details)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s)?
Checklist: