Repository navigation
docs(readme): run it in Kubernetes with the Helm chart - #456
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a short «Run it in Kubernetes» section after the Docker block: the one-line
helm installfrom the public chart (3.0.1,oci://ghcr.io/buggregator/helm-chart/buggregator) and what the chart gives.Every claim is from the chart at
546be67: PVC kept on upgrade andhelm uninstall(helm.sh/resource-policy: keep),replicaCountother than 1 fails to render (SQLite, one writer), runs as uid 65532 with a read-only root filesystem, startup/liveness/readiness probes on/api/version, SSO (UI only), Ingress, metrics + ServiceMonitor and retention as values. No claim of scaling or HA.Made with harnsy