Version Bump + Add pod deletion policy docs#1210
Draft
FireDrunk wants to merge 2 commits intolonghorn:masterfrom
Draft
Version Bump + Add pod deletion policy docs#1210FireDrunk wants to merge 2 commits intolonghorn:masterfrom
FireDrunk wants to merge 2 commits intolonghorn:masterfrom
Conversation
✅ Deploy Preview for longhornio ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
|
@FireDrunk Is the PR ready for review? |
04e4f7c to
209f75e
Compare
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.
Which issue(s) this PR fixes:
Issue (longhorn/longhorn#11876)
What this PR does / why we need it:
It adds docs for the built option.
Special notes for your reviewer:
The only changed line is at https://github.com/longhorn/website/compare/master...FireDrunk:website:feature/enable-pod-deletion?expand=1#diff-1c57a4838d4e797f2a8a816f1e0f002f02cf6fa30752482e4e69cb2fa289e86eR449
Additional documentation or context
Nope.