-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Run cred rotation every month #22977
Run cred rotation every month #22977
Conversation
The initial bi-monthly frequency was proposed given the credentials lifetime reported by this command. As all the jobs get their cluster credentials dynamically through gcloud, I think there won't be a huge impact if those are rotated on a more frequent basis. |
R: @Abacn |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
Thanks. Is the original every other month setting never working? |
It ran for the first time a little less than 2 months ago, but the creds expired before the second run. Had there been a run in between we would've most likely avoided the problem |
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.
Thanks. Let's hope it works a month later
Jenkins recently went down for a while because our creds expired. Running the IODatastores rotation job fixed it. Given that its relatively cheap, we should probably run that job every month so that we're not cutting it close on expirations. I could actually be convinced that running it even more frequently is a good idea.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.