-
Notifications
You must be signed in to change notification settings - Fork 55
config map changes for primaryfs removal #1368
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
Conversation
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
Signed-off-by: “hemalathagajendran” <“[email protected]”>
# inodeLimit: "< inode limit for Primary Fileset >" # Optional | ||
# remoteCluster: "< Remote ClusterID >" # Optional - This is only required if primaryFs is remote cluster's filesystem and this ID should have separate entry in Clusters map too. | ||
# cacert: "< Name of CA cert configmap for GUI >" # Optional | ||
# cacert: "< Name of CA cert configmap for GUI >" # Optional |
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.
I think this cacert line shouldn't be changed
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.
undone the alignment change
Signed-off-by: “hemalathagajendran” <“[email protected]”>
@@ -28,11 +28,6 @@ spec: | |||
- id: "<Primary Cluster ID>" |
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.
It’s better to avoid using the term Primary Cluster ID at both the places; instead, use Local Scale ClusterID.
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.
Basically given as such so that user should give the same primary cluster id in localScaleCluster as well
Please check the type of change your PR introduces:
How risky is this change?