https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
g
let me check
🦜 1
❤️ 1
the change will only apply to new volumes created after dropping the replica count
👍 1
for any volumes you may have created before dropping the replica count you will need to manually go and edit the replica count for those volumes
👍 1
m
Changes to the StorageClass only affect volumes created after the configuration change. For existing Longhorn volumes, I think the replica count can only be changed through the volume’s spec.
b
I changed the replica count manually for those volumes, but I'm guessing that it can't be less than the storage class?
g
storage class will not reconcile against volumes once they have been created so it should stick
👍 1
m
but I'm guessing that it can't be less than the storage class?
No, it can, as @great-bear-19718 mentioned. Alternatively, you can create a new StorageClass with the desired replica count.
b
I'd not recommend doing that, even if it works. It creates problems with Life migration or node maintenance (e.g. node crashes or Harvester upgrades). At least go with 2 replicas.
👍 1
b
Normally I'd agree with you if this weren't completely ephemeral and only needed for an experiment for a few weeks.
b
Nothing is as persistent as a temporary, experimental environment for just a few weeks 😉
b
heheh
Well it's literally a research paper that's due, but yes I see you've clearly been down this path before as well.
b
Go for it if you can extend the deadline... and add a chapter on "why not to do it like this" 🙂
b
It was a pretty big ask that came in. Hey can we have 2/3 of all your resources for like... 2 weeks?
b
Well, if you have those resources, I would not stand in their way, but also would not give any guarantees. If they can live with that, fine.
b
yeah we had a pretty long convo with them before we said yes.
👍 1
Open in Slack
PreviousNext
Powered by