Skip to main content

Helm issues


  1. 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.

Comments

  1. Amazing 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

Post a Comment

Popular posts from this blog

Saltstack and Vault integration

First install and configure vault using this tutorial: https://apassionatechie.wordpress.com/2017/03/05/hashicorp-vault/ Use the latest version of vault. Then install salt using the steps given here: https://docs.saltstack.com/en/latest/topics/installation/ If you face any issues then refer these links: https://apassionatechie.wordpress.com/2017/07/31/salt-issues/ https://apassionatechie.wordpress.com/2017/08/03/salt-stack-formulas/ Now let's integrate vault and salt so that we can access vault secrets from inside salt state. First let's add some key values into our vault. vault write secret/ssh/user1 password="abc123" Then you can check it by reading: vault read secret/ssh/user1 To allow salt to access your secrets you must firstly create a policy as follows: salt-policy.hcl [code] path "secret/*" { capabilities = ["read", "list"] } path "auth/*" { capabilities = ["read", "list","sudo",...

Salt stack issues

The function “state.apply” is running as PID Restart salt-minion with command:  service salt-minion restart No matching sls found for ‘init’ in env ‘base’ Add top.sls file in the directory where your main sls file is present. Create the file as follows: 1 2 3 base: 'web*' : - apache If the sls is present in a subdirectory elasticsearch/init.sls then write the top.sls as: 1 2 3 base: '*' : - elasticsearch.init How to execute saltstack-formulas create file  /srv/pillar/top.sls  with content: base : ' * ' : - salt create file  /srv/pillar/salt.sls  with content: salt : master : worker_threads : 2 fileserver_backend : - roots - git gitfs_remotes : - git://github.com/saltstack-formulas/epel-formula.git - git://github.com/saltstack-formulas/git-formula.git - git://github.com/saltstack-formulas/nano-formula.git - git://github.com/saltstack-f...

How to grep the output of cURL?

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