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.

Sign up for GitHub

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

Jump to bottom

gs://k8s-artifacts-cni is expensive and probably unnecessary #7584

Open
BenTheElder opened this issue Dec 5, 2024 · 3 comments
Open

gs://k8s-artifacts-cni is expensive and probably unnecessary #7584

BenTheElder opened this issue Dec 5, 2024 · 3 comments
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@BenTheElder
Copy link
Member

We were digging through the GCP billing in #sig-k8s-infra today and it turns the egress bandwidth from re-hosting https://github.com/containernetworking/plugins to gs://k8s-artifacts-cni is the largest line item after compute, by far. It's easily like 17-20k/mo.
... we should phase this out and just pull from the official upstream releases for kube-up etc.

thread in https://kubernetes.slack.com/archives/C2C40FMNF/p1733349220696569

@upodroid noticed this when we were looking into the GCS spend not continuing to shrink following the full k8s.gcr.io redirect

@upodroid suggested in the thread we could start by changing the bucket type to reduce the cost

I think longterm we want to identify what little is using this (we took a peek in cs.k8s.io, kube-up is one of the main users, but also possibly kops) and instead just use the official upstream binary releases
@BenTheElder
Copy link
Member Author

/sig k8s-infra
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Dec 5, 2024
@BenTheElder
Copy link
Member Author

/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Dec 5, 2024
This was referenced Dec 5, 2024
Merged
Open
@ameukam ameukam moved this to Backlog in SIG K8S Infra Dec 7, 2024
@BenTheElder
Copy link
Member Author

@upodroid added labels so we can collect data on this more easily.

There is some dwindling cost from the GCRs in this project and also cri tools which are both already being phased out AFAIK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
SIG K8S Infra
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BenTheElder @k8s-ci-robot