containers: Move more Dockerfiles to be based on distroless#35631
containers: Move more Dockerfiles to be based on distroless#35631def- merged 1 commit intoMaterializeInc:mainfrom
Conversation
|
Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone. PR title guidelines
Pre-merge checklist
|
9c7c3b0 to
56795d9
Compare
There was a problem hiding this comment.
It seems like we need additional changes for the orchestratord tests to pass. I assume these aren't coming up at all. I see in the cloud test describe output that environmentd has exit code 127, so we're probably trying to call something that doesn't exist.
[pod/environmentd-0/environmentd] environmentd: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory
I also suspect we will need additional changes to support ssh tunnels, since distroless doesn't ship ssh by default, and that likely relies on other libs (openssl?) which likely don't exist either. That's the only thing I know off the top of my head that we subprocess out to in environmentd/clusterd, but database folks may know others.
b4239bf to
328f4b5
Compare
328f4b5 to
46a7f0b
Compare
|
Indeed, environmentd & clusterd turned out to be too complex, so I gave up on them. |
46a7f0b to
a839800
Compare
During rolling upgrades, orchestratord may manage pods running old Ubuntu-based images (uid/gid 999 `materialize` user) alongside new distroless images (uid/gid 65534 `nonroot` user). Gate the PodSecurityContext uid/gid based on the image version to prevent permission mismatches: - environmentd/clusterd: use meets_minimum_version(V26_20_0) to select 65534 for distroless images, 999 for older Ubuntu-based images - balancerd: parse the image ref directly (balancerd switched to distroless in v26.19 via MaterializeInc#35631, earlier than environmentd/clusterd) - Make parse_image_ref public for reuse by the balancer controller Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
During rolling upgrades, orchestratord may manage pods running old Ubuntu-based images (uid/gid 999 `materialize` user) alongside new distroless images (uid/gid 65534 `nonroot` user). Gate the PodSecurityContext uid/gid based on the image version to prevent permission mismatches: - environmentd/clusterd: use meets_minimum_version(V26_20_0) to select 65534 for distroless images, 999 for older Ubuntu-based images - balancerd: parse the image ref directly (balancerd switched to distroless in v26.19 via MaterializeInc#35631, earlier than environmentd/clusterd) - Make parse_image_ref public for reuse by the balancer controller Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
During rolling upgrades, orchestratord may manage pods running old Ubuntu-based images (uid/gid 999 `materialize` user) alongside new distroless images (uid/gid 65534 `nonroot` user). Gate the PodSecurityContext uid/gid based on the image version to prevent permission mismatches: - environmentd/clusterd: use meets_minimum_version(V26_20_0) to select 65534 for distroless images, 999 for older Ubuntu-based images - balancerd: parse the image ref directly (balancerd switched to distroless in v26.19 via #35631, earlier than environmentd/clusterd) - Make parse_image_ref public for reuse by the balancer controller Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
During rolling upgrades, orchestratord may manage pods running old Ubuntu-based images (uid/gid 999 `materialize` user) alongside new distroless images (uid/gid 65534 `nonroot` user). Gate the PodSecurityContext uid/gid based on the image version to prevent permission mismatches: - environmentd/clusterd: use meets_minimum_version(V26_20_0) to select 65534 for distroless images, 999 for older Ubuntu-based images - balancerd: parse the image ref directly (balancerd switched to distroless in v26.19 via #35631, earlier than environmentd/clusterd) - Make parse_image_ref public for reuse by the balancer controller Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
balancerd: 56MB -> 23MB
fivetran-destination: 49MB -> 16MB
Similar to #35595