-
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
ramenctl: enable volsync for discovered apps #1749
ramenctl: enable volsync for discovered apps #1749
Conversation
When using discovered apps, we check for volsync support in two places in the ramenconfig. - Under multiNamespace map, we look for volsyncSupported: true key value pair - Under volsync map, we need the key "disabled" to be set to false. Ramenctl was configuring only the volsync map but not the multiNamespace one. We have to live with both the fields for now because of backward compatibility reasons. Signed-off-by: Raghavendra Talur <[email protected]>
eb35a32
to
acfe67d
Compare
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.
Nice
@@ -38,6 +38,7 @@ data: | |||
disabled: $volsync_disabled | |||
multiNamespace: | |||
FeatureEnabled: true | |||
volsyncSupported: true |
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 really use $volsync_enabled since ramenctl enabled volsync only if the env report the "volsync" feature:
ramen:
hub: hub
clusters: [dr1, dr2]
topology: regional-dr
features:
volsync: true
For example the regional-dr.yaml have "volsync: false".
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.
The check in the ramen code is an AND of !volsync.disabled and multiNamespace.volsyncSupported. The multiNamespace.volsyncSupported section is an artifact of older code and I don't want to promote the use of it. We can always keep it enabled and only modify the volsync map.
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.
Ok, lets keep it simple then.
When using discovered apps, we check for volsync support in two places in the ramenconfig.
Ramenctl was configuring only the volsync map but not the multiNamespace one.
We have to live with both the fields for now because of backward compatibility reasons.