-
Notifications
You must be signed in to change notification settings - Fork 86
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
Use Repository data in Recovery CRD #436
Conversation
Codecov Report
@@ Coverage Diff @@
## master #436 +/- ##
=====================================
Coverage 84% 84%
=====================================
Files 2 2
Lines 25 25
=====================================
Hits 21 21
Misses 2 2
Partials 2 2 Continue to review full report at Codecov.
|
apis/stash/v1alpha1/validator.go
Outdated
strings.HasPrefix(r.Spec.Repository, "replicationcontroller.") || | ||
strings.HasPrefix(r.Spec.Repository, "replicaset.") || | ||
strings.HasPrefix(r.Spec.Repository, "statefulset.") || | ||
(strings.HasPrefix(r.Spec.Repository, "daemonset.") && strings.HasSuffix(r.Spec.Repository, nodeName))) { |
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.
This nodeName
check does not work, since operator is running on different node.
`Restic` will take backup of the volume periodically with a 1-minute interval. You can verify that backup is taking successfully by, | ||
|
||
```console | ||
$ kubectl get repository deployment.stash-demo -o yaml |
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.
Why not use the new get snapshots
to confirm this?
This PR enable user to use Repository data in Recovery CRD so that they don't have to repeat backend info.
Task List: