- Helm install pod in pending state:
When you execute kubectl get events you will see the following error:
no persistent volumes available for this claim and no storage class is set or
PersistentVolumeClaim is not bound
This error usually comes in kubernetes set with kubeadm.
You will need to create persistentvolume with the following yaml file:
[code]
kind: PersistentVolume
apiVersion: v1
metadata:
name: redis-data
labels:
type: local
spec:
storageClassName: generic
capacity:
storage: 8Gi
accessModes:
- ReadWriteOnce
hostPath:
path: "/bitnami/redis"
[/code]
create pv with kubectl create -f pv-create.ymlThen you will need to create pvc with following yaml
[code]
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: redis-data
spec:
storageClassName: generic
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 8Gi
[/code]
You will need to create pvc with kubectl create -f pv-claim.ymlCheck the pvc status with kubectl get pvc with status should be bound.
curl writes the output to stderr, so redirect that and also suppress the progress: curl - v -- silent https :// google . com / 2 >& 1 | grep expire The reason why curl writes the information to stderr is so you can do: curl <url> | someprgram without that information clobbering the input of someprogram It is possible to use --stderr - as parameter, to redirect the output from stderr (default) to stdout. With this option you also should use --silent to suppress the progress bar. $ curl - v -- silent https :// google . com / -- stderr - | grep expire * expire date : 2015 - 09 - 01 00 : 00 : 00 GMT
[…] Helm issues October 17, 2017 […]
ReplyDeleteReblogged this on Linux the great.
ReplyDeleteAmazing issues here. I'm very happy to see your post. Thanks so much and I am looking ahead to touch you. Will you kindly drop me a e-mail?
ReplyDelete