Skip to content

base images without go-runner #4270

@BenTheElder

Description

@BenTheElder

What would you like to be added:

go-runner (lol!) and distroless-iptables base image versions without the go-runner binary.

So the "go-runner" image would basically just be a mirror of say, gcr.io/distroless/static-debian13.

While we're at it, we can stop forcing that variant of distroless-iptables to inherit from "go-runner", and instead directly from gcr.io/distroless/static-debian13, so distroless / debian can be updated in a single PR on the rare occasion that we actually need an update here (cacerts perhaps?)

We could do this with variants in-place perhaps?

Why is this needed:

See: https://github.com/kubernetes/kubernetes/pull/136954/changes#r2795807923

Basically, I have an approach to start building the kubernetes server images with kube-log-runner (an updated version of go-runner that already exists in kubernetes/kubernetes), which well let us consolidate go patching.

This will also let us consolidate to a single implementation of go-runner managed by sig instrumentation (kube-log-runner binary is already a release artifact for four years now, TIL).

NOTE: kube-log-runner is fully compatible, it just supports an additional flag. The proposed changes are fully compatible.

We need to continue to use images in roughly the same location / naming to avoid compatibility issues with people calling the build pointed at their base image mirrors.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/release-engIssues or PRs related to the Release Engineering subprojectkind/featureCategorizes issue or PR as related to a new feature.needs-prioritysig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions