-
Notifications
You must be signed in to change notification settings - Fork 91
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
Add probes to Fulcio deployment #506
Conversation
Signed-off-by: Cody Soyland <[email protected]>
4b580f0
to
7e952c5
Compare
}, | ||
"readinessProbe": { | ||
"description": "Readiness probe configuration", | ||
"$ref": "https://kubernetesjsonschema.dev/v1.18.1/_definitions.json#/definitions/io.k8s.api.core.v1.Probe" |
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.
Any thoughts on using these references to https://kubernetesjsonschema.dev? Not sure what implications this has, as I don't see any $ref
references within the Sigstore Helm charts.
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.
How did you generate these values ?
Signed-off-by: Cody Soyland <[email protected]>
Signed-off-by: Cody Soyland <[email protected]>
Signed-off-by: Bob Callaway <[email protected]>
fixed by #568 |
Description of the change
This adds
readinessProbe
andlivenessProbe
to the Fulcio deployment.Fulcio doesn't have health endpoints, so I'm using
/api/v1/rootCert
.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.