Skip to content
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

[bitnami/redmine] Use different liveness/readiness probes #25955

Merged
merged 1 commit into from
May 17, 2024

Conversation

dgomezleon
Copy link
Member

Description of the change

This PR aims to use different liveness/readiness probes to improve overall security and avoid unnecessary container restarts. More info.

Benefits

Increase availability and resilience.

Possible drawbacks

N/A

Applicable issues

  • fixes #

Additional information

Checklist

  • Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
  • Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
  • Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
  • All commits signed off and in agreement of Developer Certificate of Origin (DCO)

@bitnami-bot bitnami-bot added the verify Execute verification workflow for these changes label May 16, 2024
@github-actions github-actions bot requested a review from migruiz4 May 16, 2024 15:50
Signed-off-by: David Gomez <dgomezleon@vmware.com>
@dgomezleon dgomezleon merged commit bd49fad into main May 17, 2024
9 checks passed
@dgomezleon dgomezleon deleted the Redmine-probes branch May 17, 2024 10:22
fmulero pushed a commit to fmulero/charts that referenced this pull request May 22, 2024
)

Signed-off-by: David Gomez <dgomezleon@vmware.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bitnami redmine solved verify Execute verification workflow for these changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants