-
Notifications
You must be signed in to change notification settings - Fork 66
doc: Enhance documentation for Recipe #2339
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
base: main
Are you sure you want to change the base?
Conversation
41e7b48 to
2a46f2e
Compare
2a46f2e to
fe8bb20
Compare
Signed-off-by: Chris Blum <[email protected]>
e38b739 to
e24734a
Compare
Updating the recipe document with examples and comprehensive notes. Signed-off-by: Annaraya Narasagond <[email protected]>
e24734a to
7ce882f
Compare
docs/recipe.md
Outdated
| applications. While Ramen supports multiple workload | ||
| protection methods (GitOps, discovered applications, and | ||
| Recipes), Recipes are specifically designed for applications | ||
| that require: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Text is too narrow. Please wrap lines around 80 characters for easier to read text. See other docs like docs/e2e.md for example.
docs/recipe.md
Outdated
|
|
||
| ## Introduction | ||
|
|
||
| Recipes are part of Ramen's OpenShift-native Disaster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not have OpenShift in upstream docs. We can use Kubernetes instead.
| Recovery ecosystem, providing vendor-supplied or custom disaster recovery | ||
| specifications for complex stateful applications. While Ramen supports | ||
| multiple workload protection methods (GitOps, discovered applications), | ||
| Recipes are specifically designed for applications that require: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets squash this commit into the first one, it fixes issues in the first commit. We don't want to keep this in the project git history. You can squash and keep multiple signed-off-by if this was reason you made the changes in a different commit.
This PR: