-
Notifications
You must be signed in to change notification settings - Fork 21
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
feat: set quay image expiry to prevent overflow of images #212
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
name: Build SHA image for main branch | ||
|
||
on: | ||
push: | ||
branches: ['main'] | ||
|
||
jobs: | ||
workflow-build: | ||
name: Calls build-images-base workflow | ||
uses: ./.github/workflows/build-images-base.yaml | ||
secrets: inherit | ||
with: | ||
authorinoVersion: ${{ github.sha }} | ||
quayImageExpiry: 2w | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm making an assumption that SHA build are equivalent to nightly builds that we want to expire 🤔 If anyone has a better expiry value, I can update this There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Until now, SHA builds have not been equivalent to nightly builds. As of today, builds are tagged additionally with the commit SHA on top of the other, more human-friendly tag. This includes I'm not sure how I feel about breaking this link between tags, effectively building two separate images now, if this is only for the purpose of cleaning up the registry. The There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, I guess the question is then, does authorino-operator images need / want to expire images through this label? To me, it seems like it may not since the current workflow triggers on merge to main, which would build with an equivalent SHA tag. These SHA tags are kept indefinitely, but maybe that is something we want. Feature branch and release builds looks to require manual trigger of the same workflow which do not happen that regularly |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
name: Build latest image for main branch | ||
|
||
on: | ||
push: | ||
branches: ['main'] | ||
|
||
jobs: | ||
workflow-build: | ||
name: Calls build-images-base workflow | ||
uses: ./.github/workflows/build-images-base.yaml | ||
secrets: inherit |
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.
Is this really what we want? This will break with the single manifest link between builds.
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.
I don't see how we can add the expire label for different types of builds unless we do this since latest & SHA builds are usually the same on merge to main.
Branch + SHA build would only happen if the workflow is triggered manually currently.