Hi, you have covered base images vs distroless images in your article. A lot of organizations don't yet have the tooling required to maintain distroless images

Hi, you have covered base images vs distroless images in your article. A lot of organizations don't yet have the tooling required to maintain distroless images (since that tooling extends all the way to developer machines). Have you considered a hybrid option, where in GKE, you automatically keep this base image layer auto-updated when running on cos? It could give organizations that don't have distroless capability to still use vanilla docker tooling, but still get the same benefits of distroless at runtime (and potential of increased adoption it might drive to GKE)?