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

address GCS bucket for downloads in host instead of url path prefix #5727

Closed
BenTheElder opened this issue Aug 16, 2023 · 13 comments
Closed

address GCS bucket for downloads in host instead of url path prefix #5727

BenTheElder opened this issue Aug 16, 2023 · 13 comments
Assignees
@ameukam
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.
Milestone
v1.32

Comments

@BenTheElder
Copy link
Member

We discussed with Fastly that we should probably address the bucket name in the host instead of the URL path so we can more easily switch buckets later without busting the cache.

This is a low-prio backlog item as due to #5726 there doesn't appear to be much of a cache to bust.
@BenTheElder
Copy link
Member Author

cc @ameukam (also present in the discussion w/ fastly)

@ameukam
Copy link
Member

ameukam commented Sep 4, 2023

/milestone v1.29
/priority important-longterm
/sig k8s-infra

/assign

@k8s-ci-robot k8s-ci-robot added this to the v1.29 milestone Sep 4, 2023
@k8s-ci-robot k8s-ci-robot added 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. labels Sep 4, 2023
@ameukam ameukam modified the milestones: v1.29, v1.30 Dec 8, 2023
@ameukam ameukam mentioned this issue Mar 1, 2024
Merged
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2024
@ameukam
Copy link
Member

ameukam commented Mar 7, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2024
@BenTheElder
Copy link
Member Author

Is this done now? #6509

@ameukam
Copy link
Member

ameukam commented Apr 18, 2024

Is this done now? #6509

No. Need to be deployed in prod.
Will get some bandwidth soon to get this deployed.

@ameukam ameukam mentioned this issue Apr 18, 2024
Closed
@ameukam
Copy link
Member

ameukam commented Apr 18, 2024

/milestone v1.31

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.30, v1.31 Apr 18, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2024
@ameukam
Copy link
Member

ameukam commented Jul 17, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2024
@ameukam
Copy link
Member

ameukam commented Aug 21, 2024

/milestone v1.32

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.31, v1.32 Aug 21, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 19, 2024
@ameukam
Copy link
Member

ameukam commented Nov 19, 2024

@BenTheElder I think we can call this done ?

@BenTheElder
Copy link
Member Author

Thank you!
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ameukam ameukam

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.
Projects
None yet
Milestone
v1.32
Development

No branches or pull requests
4 participants
@BenTheElder @ameukam @k8s-ci-robot @k8s-triage-robot