Skip to content
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

storageclass:microk8s-hostpath reclaim policy change #11

Open
balasu opened this issue Feb 9, 2022 · 0 comments
Open

storageclass:microk8s-hostpath reclaim policy change #11

balasu opened this issue Feb 9, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@balasu
Copy link
Collaborator

balasu commented Feb 9, 2022

Hi
Currently storageClass=microk8s-hostpath has a reclaimpolicy of delete, if any add-on is using it and when someone accidentally do disable and enable the storageclass, pvc connected to the storageclass will lose data. or if the add-on has explicitly call the storage add-on from its script, if user disable/enable their add-on, pvc is lost.

root@localhost:~# microk8s kubectl describe sc
Name:            microk8s-hostpath
IsDefaultClass:  Yes
Annotations:     kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.kubernetes.io/is-default-class":"true"},"name":"microk8s-hostpath"},"provisioner":"microk8s.io/hostpath"}
,storageclass.kubernetes.io/is-default-class=true
Provisioner:           microk8s.io/hostpath
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

kindly change to ReclaimPolicy: Retain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants