[GitHub] [camel-k] asifdxtreme opened a new issue #898: Camel-k-cache not able to create PVC (pod has unbound immediate PersistentVolumeClaims)

[GitBox <gi...@apache.org>]

asifdxtreme opened a new issue #898: Camel-k-cache not able to create PVC (pod has unbound immediate PersistentVolumeClaims)
URL: https://github.com/apache/camel-k/issues/898
 
 
   I am running camel-k on K8s(v1.15.1), camel-k-operator comes up fine but the `came-k-cache` always remains in the `Pending` phase, as per the logs of camel-k-cache pod the PVC Claim fails and it's not able to schedule. Below are the logs from the env.
   
   ```
   ~$ kubectl get pods
   NAME                               READY   STATUS    RESTARTS   AGE
   camel-k-cache                      0/1     Pending   0          11h
   camel-k-operator-85699785f-22t9m   1/1     Running   0          11h
   
   ```
   ```
   ~$ kubectl describe pod camel-k-cache
   Name:         camel-k-cache
   Namespace:    default
   Priority:     0
   Node:         <none>
   Labels:       <none>
   Annotations:  <none>
   Status:       Pending
   IP:           
   Init Containers:
     create-kaniko-cache:
       Image:      busybox
       Port:       <none>
       Host Port:  <none>
       Command:
         mkdir
         -p
         /workspace/cache
       Environment:  <none>
       Mounts:
         /var/run/secrets/kubernetes.io/serviceaccount from default-token-xldvs (ro)
         /workspace from camel-k-builder (rw)
   Containers:
     warm-kaniko-cache:
       Image:      gcr.io/kaniko-project/warmer:v0.9.0
       Port:       <none>
       Host Port:  <none>
       Args:
         --cache-dir=/workspace/cache
         --image=fabric8/s2i-java:3.0-java8
       Environment:  <none>
       Mounts:
         /var/run/secrets/kubernetes.io/serviceaccount from default-token-xldvs (ro)
         /workspace from camel-k-builder (rw)
   Conditions:
     Type           Status
     PodScheduled   False 
   Volumes:
     camel-k-builder:
       Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
       ClaimName:  camel-k
       ReadOnly:   false
     default-token-xldvs:
       Type:        Secret (a volume populated by a Secret)
       SecretName:  default-token-xldvs
       Optional:    false
   QoS Class:       BestEffort
   Node-Selectors:  <none>
   Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                    node.kubernetes.io/unreachable:NoExecute for 300s
   Events:
     Type     Reason            Age                    From               Message
     ----     ------            ----                   ----               -------
     Warning  FailedScheduling  2m32s (x480 over 11h)  default-scheduler  pod has unbound immediate PersistentVolumeClaims
   
   ```
   ```
   ~$ kubectl describe pvc camel-k
   Name:          camel-k
   Namespace:     default
   StorageClass:  
   Status:        Pending
   Volume:        
   Labels:        app=camel-k
   Annotations:   <none>
   Finalizers:    [kubernetes.io/pvc-protection]
   Capacity:      
   Access Modes:  
   VolumeMode:    Filesystem
   Mounted By:    camel-k-cache
   Events:
     Type    Reason         Age                    From                         Message
     ----    ------         ----                   ----                         -------
     Normal  FailedBinding  3m1s (x2863 over 11h)  persistentvolume-controller  no persistent volumes available for this claim and no storage class is set
   
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services