Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slim version of the cilium-cli image #2780

Open
marcofranssen opened this issue Aug 29, 2024 · 4 comments · May be fixed by #2782
Open

Slim version of the cilium-cli image #2780

marcofranssen opened this issue Aug 29, 2024 · 4 comments · May be fixed by #2782
Assignees
Labels
kind/feature New feature or request priority/release-blocker This issue will prevent the release of the next version of Cilium.

Comments

@marcofranssen
Copy link
Contributor

marcofranssen commented Aug 29, 2024

Proposal / RFE

Is your feature request related to a problem?

The quay.io/cilium/cilium-cli-ci:latest image is quite large (2.23GB). We use this image in a k8s Job to bootstrap the CNI on our fresh clusters. Due to the large image size it takes several minutes in EKS environments to have the image pulled in at our fargate Node that is used to bootstrap the CNI for our karpenter managed nodes.

Trying to speed up our bootstrapping time, we also use image pull-through cache in ECR, so the image is in the same region as our cluster, but this barely improves the image pull speed.

Describe the solution you'd like

Having a slim image (e.g. busybox/alpine/scratch/distroless) would reduce the image pull time drastically which would speed up our cluster bootstrapping. Several MB compared to 2.23GB.

Futhermore it would be great if the image tagging strategy would include some version tagging, so it is easy to pick a specific cilium version and choose the distro variant of the image (slim/distroless, whatever we decide to make available).

Note

If feature request is accepted, happy to take a stab at adding a Dockerfile/updating the existing image (depending on what we choose as a solution direction). I would also need to understand why some of the dependencies are in the current image like the google sdk and such. (could we leave those out for proper functioning, or could we make cloud provider specific images).

@marcofranssen marcofranssen added the kind/feature New feature or request label Aug 29, 2024
@marcofranssen marcofranssen linked a pull request Sep 2, 2024 that will close this issue
Copy link

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Oct 29, 2024
@marcofranssen
Copy link
Contributor Author

There are 2 PRs to finalize this.

#2842
#2782

@github-actions github-actions bot removed the stale label Oct 30, 2024
@michi-covalent michi-covalent added the priority/release-blocker This issue will prevent the release of the next version of Cilium. label Nov 11, 2024
@michi-covalent
Copy link
Contributor

let's take care of this before the december release cc @tklauser

@marcofranssen
Copy link
Contributor Author

marcofranssen commented Nov 25, 2024

@tklauser @michi-covalent I updated the PR with another rebase so it is fully in sync with main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/release-blocker This issue will prevent the release of the next version of Cilium.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants