Open BenTheElder opened 1 year ago
cc @ameukam (also present in the discussion w/ fastly)
/milestone v1.29 /priority important-longterm /sig k8s-infra
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Is this done now? https://github.com/kubernetes/k8s.io/pull/6509
Is this done now? #6509
No. Need to be deployed in prod. Will get some bandwidth soon to get this deployed.
/milestone v1.31
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/milestone v1.32
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 https://github.com/kubernetes/k8s.io/issues/5726 there doesn't appear to be much of a cache to bust.