issue-1803: Updated Elasticsearch example #1840
Merged
Conversation
This file contains 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
|
Thanks for submitting this pull request 🎉. The team will review it soon and get back to you. If you haven't already, please take a moment to review our project contributing guideline and Code of Conduct document. |
PrasadG193
reviewed
Jan 4, 2023
|
|
||
| The command will configure a location where artifacts resulting from Kanister | ||
| data operations such as backup should go. This is stored as a `profiles.cr.kanister.io` | ||
| *CustomResource (CR)* which is then referenced in Kanister ActionSets. Every ActionSet | ||
| requires a Profile reference to complete the action. This CR (`profiles.cr.kanister.io`) | ||
| can be shared between Kanister-enabled application instances. | ||
|
|
||
| Once Elasticsearch is running, you can populate it with some data. Follow the instructions that get displayed by running command `helm status my-release` to connect to the application. | ||
| ### Create Blueprint |
There was a problem hiding this comment.
Should Create Blueprint be under Protect the Application` section?
There was a problem hiding this comment.
In other examples, we have create blueprint before protect application section. Hence kept it similar
shahpratikr
force-pushed
the
pratik/issue-1803
branch
from
ea6f879 to
70edd9f
Compare
pavannd1
reviewed
Jan 5, 2023
shahpratikr
force-pushed
the
pratik/issue-1803
branch
from
70edd9f to
4f11d43
Compare
shahpratikr
force-pushed
the
pratik/issue-1803
branch
from
4f11d43 to
bbb4d65
Compare
shahpratikr
force-pushed
the
pratik/issue-1803
branch
from
bbb4d65 to
245f3b6
Compare
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.
Change Overview
This change updates steps in elasticsearch example for latest helm chart.
Pull request type
Please check the type of change your PR introduces:
Issues
Test Plan
Verified steps in a digital ocean cluster.