-
Notifications
You must be signed in to change notification settings - Fork 913
Remove references to k8s-staging-release-test #947
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
Conversation
/area release-eng |
@@ -217,16 +215,6 @@ for repo in "${RELEASE_STAGING_PROJECTS[@]}"; do | |||
color 6 "Empowering ${RELEASE_VIEWERS} as project viewers in ${PROJECT}" | |||
empower_group_as_viewer "${PROJECT}" "${RELEASE_VIEWERS}" | |||
|
|||
# TODO(justaugustus): Remove once the k8s-releng-prod GCP project is |
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.
Just for reference...
Moving releng KMS was done as part of kubernetes/release#1163.
/lgtm Agreed we should hold deletion until working hours. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justaugustus, spiffxp 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 |
/hold cancel |
|
Encountered while running
ensure-staging-storage.sh
for all projects (ref: #857 (comment)).The change that caused this (#742) landed 2020-04-13. Taking ~2 months to surface isn't great.
Per #857 (comment) I think this just about closes out kubernetes/release#1161 but I'm avoiding using the "fixes" keyword to ensure we can verify.
/hold
We don't have automated deletion of projects so someone (probably me) will have to manually delete k8s-staging-release-test to finish this. I'm not about to do so off-hours.