Installation Issues

This section provides recommended solutions to some commonly seen problems during deployment:

Unable to Pull Images From the Aizen Repository

ImagePullBackOff will be seen when you describe the pod using the command:

kubectl describe pod <PODNAME>

kubectl get pods -n <NAMESPACE>

Check if the Aizen Repository secret name used during deployment is missing in your namespace, or if the Aizen Repository credential name was misspelled during deployment:
```
kubectl get secrets -n <NAMESPACE>
```

If the names are missing, create them by running this command:

kubectl create secret docker-registry aizenrepo-creds 
--docker-username=aizencorp 
--docker-password=<YOUR SECRET> 
-n <NAMESPACE>

When the state of specified pods is not in a Running state, run this command:
```
kubectl -n <NAMESPACE> get pods
```

Check the describe output for the pod:

kubectl -n <NAMESPACE> describe pod <PODNAME>

This error is seen during the execution of console commands.

Validate that the storage class has the property ALLOWVOLUMEEXPANSION set to true:
```
kubectl describe sc <storage classname>
```
Increase the storage size for the PersistentVolumeClaim (PVC) without any downtime:
```
kubectl get pvc -n <namespace>
```
Edit the storage size of the PVC:
```
kubectl edit pvc <pvc name> -n <namespace>
```
Edit and increase the storage size for all the PVCs listed by the previous command.

Delete the storage StatefulSet:

kubectl -n <namespace> get statefulset
 
kubectl delete statefulset --cascade=orphan <statefulset name> -n namespace

Redeploy the chart to re-create storage StatefulSet:

helm upgrade <existing release name> <chartname> -n <>namespace>

The storage StatefulSet will be created with the updated PVC size:
```
kubectl -n <namespace> get pvc
```

Last updated 4 months ago