-
Notifications
You must be signed in to change notification settings - Fork 58
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
e2e: describes configs used in config.yaml.sample #1767
base: main
Are you sure you want to change the base?
Conversation
* Added comments for different options except for pvc properties(self explaining) * Shows sample clusters, can be uncommented out to make it easy to configure kubeconfig paths. Signed-off-by: Parikshith <[email protected]>
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.
Looks good, see minor comments.
@@ -1,11 +1,35 @@ | |||
--- | |||
# Configuration file for RamenDR E2E testing on Regional DR. | |||
|
|||
# Name of the channel used for the Channel CR (utilized by Subscription CRs). |
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.
Also by ApplicationSet, so we can just mention that OCM is using this to pull the application from git.
|
||
# Sample cluster configurations (commented out by default): | ||
# Uncomment and edit the following lines to provide the kubeconfig paths | ||
# for your test clusters. |
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 can remove "(commented by default)".
# Sample cluster configurations (commented out by default): | ||
# Uncomment and edit the following lines to provide the kubeconfig paths | ||
# for your test clusters. | ||
|
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 remove the blank line - the all the other comments are right above the yaml item, so this should be right above the "clusters:".
Resolves #1765