Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
1
Description
Currently the CouchbaseCluster.Spec.Backup.NodeSelector only applies to backup jobs, it would be good to allow restore jobs to also be configurable in this way.
A potential quick fix would be to reuse the same node selector for restore jobs - but does everyone want backup and restore to share node selectors (I imagine most would be ok with it)?
Should we provide a separate field for restore (CRD update) that can default to the existing backup one? We could provide a quick fix using the backup one for now and a longer term change to provide a separate CRD update that defaults to the existing one.
Attachments
Issue Links
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Link | This issue relates to CBSE-10394 [ CBSE-10394 ] |
| Fix Version/s | 2.3.0 [ 17600 ] |
| Description | Currently the CouchbaseCluster.Spec.Backup.NodeSelector only applies to backup jobs, it would be good to allow restore jobs to also be configurable in this way. |
Currently the CouchbaseCluster.Spec.Backup.NodeSelector only applies to backup jobs, it would be good to allow restore jobs to also be configurable in this way.
A potential quick fix would be to reuse the same node selector for restore jobs - but does everyone want backup and restore to share node selectors (I imagine most would be ok with it)? Should we provide a separate field for restore (CRD update) that can default to the existing backup one? We could provide a quick fix using the backup one for now and a longer term change to provide a separate CRD update that defaults to the existing one. |
| Component/s | documentation [ 14113 ] |
| Fix Version/s | 2.2.1 [ 17700 ] |
| Assignee | Simon Murray [ simon.murray ] | Prateek Kumar [ prateek.kumar ] |
| Link | This issue blocks K8S-2276 [ K8S-2276 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 2.3.0 [ 17600 ] |