Verifying the Pods

10.3 Verifying the Pods

Verifying the pods for ELK depends on whether you are using NFS or file system storage, or block storage for your persistent volume.

NFS or File System Storage

If you are using Oracle Unified Directory (OUD) with NFS or file system storage, a new logstash pod will be created.

Run the following command to check the logstash pod is created correctly:

kubectl get pods -n <namespace>

For example:

kubectl get pods -n oudns

The output should look similar to the following:

NAME                                  READY   STATUS      RESTARTS   AGE
oud-ds-rs-0                           1/1     Running     0          150m
oud-ds-rs-1                           1/1     Running     0          143m
oud-ds-rs-2                           1/1     Running     0          137m
oud-ds-rs-logstash-5dc8d94597-knk8g   1/1     Running     0          2m12s
oud-pod-cron-job-27758370-wpfq7       0/1     Completed   0          66m
oud-pod-cron-job-27758400-kd6pn       0/1     Completed   0          36m
oud-pod-cron-job-27758430-ndmgj       0/1     Completed   0          6m33s

Note:

Wait a couple of minutes to make sure the pod has not had any failures or restarts. If the pod fails you can view the pod log using:

kubectl logs -f oud-ds-rs-logstash-<pod> -n oudns

If the logstash pod has problems, see Troubleshooting Pod and Logstash Errors.

Block Storage

If you are using OUD with block devices, the logstash pod will run as a separate sidecar container in the OUD pods.

Run the following command to check the sidecar pod is created:
```
kubectl get pods -n <namespace>
```
For example:
```
kubectl get pods -n oudns
```
The output should look similar to the following:
```
NAME                                  READY   STATUS      RESTARTS   AGE
oud-ds-rs-0                           2/2     Running     0          24m
oud-ds-rs-1                           2/2     Running     0          17m
oud-ds-rs-2                           2/2     Running     0          10m
etc..
```
Notice the pods oud-ds-rs-0 - oud-ds-rs-2 have a READY status of 2/2.
Note:
The pods will terminate one at a time and restart to add the sidecar logstash container. For example oud-ds-rs-2 will terminate and restart. oud-ds-rs1 will not terminate until oud-ds-rs-2 is at READY 2/2. If any of the pods fail, you can view the pod logs using:
```
kubectl logs -f oud-ds-rs-<pod> -c oud-ds-rs-logstash -n oudns
```
If the pods have problems starting, see Troubleshooting Pod and Logstash Errors.