Conversation
This branch has not been deployed
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
1 participant
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 Backup and Restore section to the Enterprise README. The chart has no backup support of its own, so this covers how the built-in
influxdb3backup and restore commands fit a Helm install: which pod runs them, where the backups end up, whyhelm uninstalltakes them along on file storage, and what a restore into a new cluster needs from the release. It also corrects the Clean Up PVCs note, which said no PVC is deleted on uninstall; the file object-store PVC is.Two points describe product behaviour found while testing on kind, not anything in the chart. On 3.11.0 through 3.11.5 the queriers have to be restarted after a restore before they see tables created afterwards (3.10.6 does not do this), and a restore interrupted by a compactor restart stays
in_progressuntil it is run again. The README documents the workaround for both.Not tested on a cluster: the GCS lease note, the TLS flags, the enginePathPrefix path and the trial licence file were taken from the 3.11 source and docs; everything else was run on kind with the chart's defaults.
0.14.3 sits above #850 (0.14.1) and #852 (0.14.2), so this should land after both.