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
Backfillredis helm chart. #398
Conversation
Just to check, can we get the logs for the job once it finishes? Do we need to configure anything to prevent something else from coming along and scheduling another job and removing the logs? |
Yes, the job runs, and if it fails, it will retry up to 6 times by default. If it succeeds, yay! We'll have logs available from the normal console / kubectl way. |
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.
cc @k4leung4
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.
looks good
thanks
640f937
to
f1fcbdc
Compare
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Signed-off-by: Ville Aikas <vaikas@chainguard.dev>
Also note that when I ran
it picked up the changes from #409 to README. I didn't actually change them in this PR. |
Signed-off-by: Ville Aikas vaikas@chainguard.dev
Description of the change
We need to run a job in the cluster to backfill redis. The code is here:
sigstore/rekor#1163
So this wraps it in a helm chart
Existing or Associated Issue(s)
Additional Information
Checklist
Chart.yaml
according to semver. Where applicable, update and bump the versions in any associated umbrella chartvalues.yaml
and added to the README.md. The helm-docs utility can be used to generate the necessary content. Usehelm-docs --dry-run
to preview the content.ct lint
command.