Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

PVCs in migration guide looks incorrect #110

Closed
dkirrane opened this issue Apr 29, 2019 · 2 comments · Fixed by #114
Closed

PVCs in migration guide looks incorrect #110

dkirrane opened this issue Apr 29, 2019 · 2 comments · Fixed by #114

Comments

@dkirrane
Copy link

dkirrane commented Apr 29, 2019

In the migration example I can see a couple of issues:

  • Client node defines a PVC
  • Data node doesn't define a PVC

Also, even there doesn't seem to be a way to disable PVC creation for a Client node. PVC always gets created.

@Crazybus
Copy link
Contributor

Client node defines a PVC

We had an issue discussing this but it looks like it was closed for some reason. Right now it isn't possible to disable the PVC but is as simple as adding a value to disable it. If no one else picks it up I'll get around to it shortly.

#58 (comment)

Data node doesn't define a PVC

It does, although right now it uses the default

volumeClaimTemplate:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 30Gi
values that are specified

I'll make this the new "allow creation of pvcs to be disabled" issue

Crazybus added a commit that referenced this issue May 1, 2019
Certain node roles do not require any persistent data. Setting
`persistence.enabled: false` will allow nodes to be created without
persistent volumes.

Fixes: #58
Fixes: #110
@Crazybus
Copy link
Contributor

Crazybus commented May 1, 2019

Opened #114 which makes it possible to disable the persistent volume and updated the migration guide.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants