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
remove retention policy for staging buckets #116222
remove retention policy for staging buckets #116222
Conversation
/lgtm |
LGTM label has been added. Git tree hash: 23dc5d9214c15bb6d12d3b657c7e52991499d13c
|
Any new bucket should be created without retention policy. |
cc @wojtek-t @aojea "storage/cacher: Test_newReadyRacy" failed in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/116222/pull-kubernetes-unit/1631324028675297280 opened #116225 to track /retest |
/retest |
👀 |
when we circle back to this we will want to set a lifecycle policy (TTL rule) instead of retention policy (forced to keep) 😅 |
Real verify failure: In ./cluster/gce/util.sh line 329:
retention_period="1d" # https://cloud.google.com/storage/docs/bucket-lock#retention-periods
^--------------^ SC2034 (warning): retention_period appears unused. Verify use (or export if used externally). Recommend adding a |
5ba9b4d
to
27dbb35
Compare
Follow-up of: - kubernetes#115634 The current retention policy prevent creation or update of new objects until the existing one are deleted based on the retention period. Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
27dbb35
to
4719855
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
LGTM label has been added. Git tree hash: 3152f32f8480bc78853456c6cbcb5fd48cbf5ca7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, BenTheElder, liggitt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/triage accepted |
/retest |
/retest |
2 similar comments
/retest |
/retest |
Follow-up of:
The current retention policy prevent creation or update of new objects until the existing one are deleted based on the retention period.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: