-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Snapshot and restore volumes by default #45
Conversation
Can one of the admins verify this patch? |
@@ -43,7 +43,7 @@ metadata: | |||
name: nginx-deployment | |||
namespace: nginx-example | |||
spec: | |||
replicas: 2 | |||
replicas: 1 |
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 "cheated" a bit in here to label one node with app=nginx
to ensure pods from the deployment all land on the same node. @abiogenesis-now I think it's cleaner this way, and then we can remove the node labeling bit from the docs. WDYT?
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.
Landing on the same node wasn’t the problem for me. With the PVC in Minikibe the two replicas are contending for ownership since it is not a storage class that allows of multiple attachments Via the ReadWriteOnce
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.
Ah, interesting! I think we'll probably go ahead and remove the node labeling bit from that doc, but let's wait for @abiogenesis-now to chime in before doing so.
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.
Yeah, I think that makes sense, and it'll simplify the docs a lot. @ncdc @jrnt30 We also do need to make docs changes to cloud-provider-specifics.md
:
-
Remove the first node-labeling example from the snapshot example instructions (This relates to discussion above)
-
Update the basic (no-PVs) example command to include
--snapshot-volumes=false
and--restore-volumes=false
-
It might be clearer to also update the snapshot example section to either specify
--snapshot-volumes=true
and--restore-volumes=true
, or remove the flags entirely since itstrue
by default
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 might be clearer to also update the snapshot example section to either specify --snapshot-volumes=true and --restore-volumes=true, or remove the flags entirely since its true by default
Let's remove them.
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 have removed the additional notes, thanks!
My preference would be to leave the --snapshot-volumes=false
for the basic example to not muddle the waters as Ark works just fine if you don't have PVs but the setting is enabled. If you would still like that change, I can do so.
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.
Sorry, I was referring to removing the =true
ones!
ok to test |
LGTM. @skriss PTAL |
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.
@jrnt30 I think you might have missed adding --snapshot-volumes=false
and --restore-volumes=false
in lines 289-304 of cloud-provider-specifics.md
?
Oh @jrnt30 misread your comment, you are intentionally leaving out those |
I left it out intentionally because it isn't necessary, yes. If I were to do a create/restore with the flags set to That being said, I can add those in explicitly if you think it is adding value or I'm overlooking the importance of said feature. |
I'm fine not including the flags |
Probably good to remove the flags from the 2 command snippets here: use cases @abiogenesis-now also has an updated architecture diagram that removes the flag. Otherwise LGTM! |
Thanks for making the docs changes @jrnt30, LGTM. Before merging, it looks like a download backup commit made its way into this branch that should be pulled out, and you need to rebase. |
@skriss I do not see the file you are referring to, can you be more specific perhaps? |
Oh...right, wrong branch... Yes, I will correct this |
@jrnt30 please rebase |
Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
- The two replicas contend for single PVC with the defined toplogy. Could adjust to SS but kept it simple for now Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
- Removed explicit setting of snapshot flags - Removed node selector on replicaset to reduce manual steps for users Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
Signed-off-by: Justin Nauman <justin.r.nauman@gmail.com>
LGTM. @abiogenesis-now & @skriss, please take 1 more look. Thanks! |
LGTM. |
NOTE: Additionally changes default for replicas on the PV example so that it will bootstrap properly.