You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
/kind bug
NOTE: This is a clone of kubernetes/kubernetes#66222. The original fix was done inside kubernetes core and didn't fix minikube. I will provide a PR for minikube shortly.
What happened:
Not able to change the default storage class.
What you expected to happen:
Default storage class to change.
How to reproduce it (as minimally and precisely as possible):
storageclass "standard" patched
$ kubectl describe sc standard
Name: standard
IsDefaultClass: No
Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"storageclass.beta.kubernetes.io/is-default-class":"true"},"labels":{"addonmanager.kubernetes.io/mode":"Reconcile"},"name":"standard","namespace":""},"provisioner":"k8s.io/minikube-hostpath"}
,storageclass.beta.kubernetes.io/is-default-class=false
Provisioner: k8s.io/minikube-hostpath
Parameters: <none>
ReclaimPolicy: Delete
VolumeBindingMode: Immediate
Events: <none>
$ kubectl get sc
NAME PROVISIONER AGE
rook-ceph-block (default) ceph.rook.io/block 14h
standard k8s.io/minikube-hostpath 14h
But after few mins.
$ kubectl get sc --watch
NAME PROVISIONER AGE
rook-ceph-block (default) ceph.rook.io/block 14h
standard k8s.io/minikube-hostpath 14h
standard (default) k8s.io/minikube-hostpath 14h
$ kubectl get sc
NAME PROVISIONER AGE
rook-ceph-block (default) ceph.rook.io/block 14h
standard (default) k8s.io/minikube-hostpath 14h
$ kubectl describe sc rook-ceph-block
Name: rook-ceph-block
IsDefaultClass: Yes
Annotations: storageclass.beta.kubernetes.io/is-default-class=true
Provisioner: ceph.rook.io/block
Parameters: clusterNamespace=rook-ceph,pool=replicapool
ReclaimPolicy: Delete
VolumeBindingMode: Immediate
Events: <none>
Anything else we need to know?:
Tried to remove the annotation but no luck.
Please provide the following details:
Environment: Ubuntu 16.04
Minikube version (use minikube version): 0.31
OS (e.g. from /etc/os-release):
VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): none
ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION):
Install tools:
Others:
The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
Change the policy for the minikube-hostpath storage class addon from
Reconcile to EnsureExists. When it's set to reconcile, it's impossible
to change the default storage class in Minikube because it will keep
setting the minikube-hostpath storageclass to default.
Ported from kubernetes/kubernetes#66235
jasoncwik
added a commit
to jasoncwik/minikube
that referenced
this issue
Dec 29, 2018
Change the policy for the minikube-hostpath storage class addon from
Reconcile to EnsureExists. When it's set to reconcile, it's impossible
to change the default storage class in Minikube because it will keep
setting the minikube-hostpath storageclass to default.
Ported from kubernetes/kubernetes#66235
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
/kind bug
NOTE: This is a clone of kubernetes/kubernetes#66222. The original fix was done inside kubernetes core and didn't fix minikube. I will provide a PR for minikube shortly.
What happened:
Not able to change the default storage class.
What you expected to happen:
Default storage class to change.
How to reproduce it (as minimally and precisely as possible):
But after few mins.
Please provide the following details:
Environment: Ubuntu 16.04
Minikube version (use
minikube version
): 0.31cat ~/.minikube/machines/minikube/config.json | grep DriverName
): nonecat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Output of
minikube logs
(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: