-
Notifications
You must be signed in to change notification settings - Fork 840
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
prow-build-trusted: Add PVC for publishing-bot #5685
Conversation
Related to: - kubernetes/publishing-bot#353 Add a PVC that will be used publishing-bot as a prowjob Signed-off-by: Arnaud Meukam <[email protected]>
cc @akhilerm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam 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 |
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.
q: There can be cases where the contents stored in the publishing bot PV can get corrupted sometime and we will have to delete and recreate it.
In such a scenario, how can someone easily delete and recreate the PVC ?
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.
Since the publishing-bot pod is handled by the prowjob, I suspect (I think I'm wrong) that for each run of the prowjob we'll get a new PV (or do we want to create the PV manually? ). If that's the case, cleanup can handled differently. One alternative could be the usage of ephemeral storage in the podSpec.
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.
Nope. We dont to have a new PV for everyrun, that will defeat the purpose. The PV is used so that we dont have to download all the repos everytime. And ephemeral storage also wont suffice our needs. A PV is what we need, and whatever changes in this are good. I was thinking of methods on how to clean it incase if it gets corrupted.
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.
Anyways, the cleanup part we can think of later in a separate PR once the publishing-bot is migrated to test-infra.
IMHO, for adding the PVC this is good. Thank you
labels: | ||
app: publisher | ||
spec: | ||
storageClassName: "premium-rwo" |
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 same as ssd
storage class?
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.
Yes
kind: PersistentVolumeClaim | ||
metadata: | ||
name: publishing-bot-pvc | ||
namespace: test-pods |
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.
q: Is the same namespace in which all the prow test jobs run?
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.
Yes
/lgtm |
q: @ameukam Is this change rolled out manually. or is the PVC created automatically? |
Related to:
Add a PVC that will be used publishing-bot as a prowjob