-
Notifications
You must be signed in to change notification settings - Fork 35
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
OVA: generate random names for NFS pv and PVS used for migration #757
Conversation
Signed-off-by: Bella Khizgiyaev <[email protected]>
Signed-off-by: Bella Khizgiyaev <[email protected]>
Quality Gate passedIssues Measures |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #757 +/- ##
=========================================
+ Coverage 0 16.92% +16.92%
=========================================
Files 0 88 +88
Lines 0 17877 +17877
=========================================
+ Hits 0 3025 +3025
- Misses 0 14607 +14607
- Partials 0 245 +245
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Name: pvcName, | ||
Namespace: r.Plan.Spec.TargetNamespace, | ||
Labels: labels, | ||
GenerateName: pvcNamePrefix, |
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.
you can call getEntityPrefixName
here directly I think
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.
+1 for this approach
edit: there's a typo in the title of the PR, randon -> random
Signed-off-by: Bella Khizgiyaev <[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.
it feels like we're still putting too much "effort" to generate the prefix which is less important when the postfix is generated but we can check that separately
An issue has been identified where manually constructed names for PVCs lead to migration failures, especially during restarts or when reusing the same plan names. This occurs because of conflicts with existing PVCs. To address this, the implementation now utilizes
GeneratedName
to ensure unique naming and prevent collisions. Correspondingly, the cleanup process has been changed to accommodate these changes.