add fastly purging logic to krel and purge all related markers everytime a new marker is pushed#4280
Merged
k8s-ci-robot merged 1 commit intokubernetes:masterfrom Feb 24, 2026
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
We are caching the release markers at dl.k8s.io. Details are at https://kubernetes.slack.com/archives/CJH2GBF7Y/p1770744489128559
This PR does a few things:
Surrogate-Key: [prod|ci]-markersheaders when uploading markers, which allows Fastly to track these files with these headers and purge them together.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?