Home

Oc get pods status running

$ oc get pods. For example: $ oc get pods -n openshift-console NAME READY STATUS RESTARTS AGE console-698d866b78-bnshf 1/1 Running 2 165m console-698d866b78-m87pm 1/1 Running 2 165m. Add the -o wide flags to view the pod IP address and the node where the pod is located Pod failures return explicit error states that can be observed in the status field in the output of oc get pods. Pod error states cover image, container, and container network related failures. The following table provides a list of pod error states along with their descriptions. Inspecting pod and container log One of the rare situations where you encounter is that Pod get stuck in Pending status. Thus, when you run: oc get pods. You will see Pod(s) get stuck in Pending STATUS. To troubleshoot, there are multiple ways. But when you do, oc logs -f POD_NAME. Nothing may show. Try. oc get events. And you see: no nodes available to schedule pods I have got the list of pods in running state with below Ansible playbook. - name: get calico pods command: oc get pods -n calico-system register: calico_pods - name: list of pods in running st..

A bit more ugly, but at least it's not the desired (as done by Javier Salmeron) but the true status of the Pod: kubectl -n MYNAMESPACE describe pods MYPOD | grep ^Status: | head -1 | awk '{print $2}' | tr -d '\n $ oc get pods NAME READY STATUS RESTARTS AGE ruby-hello-world-1-build 0/1 Completed 0 9d ruby-hello-world-1-sg623 1/1 Running 0 9d Current Result Now, the --show-all flag works with the default output, but doesn't when the output is set to name In my project, I have a number of pods as shown below. $ oc get pods NAME READY STATUS RESTARTS AGE harbor-harbor-chartmuseum-5456c9d756-97pdd 1/1 Running 0 38h harbor-harbor-clair-654dcfd8bf-kgxk4 2/2 Running 0 38h harbor-harbor-core-76d64c78b6-kv24c 1/1 Running 1 38h harbor-harbor-database- 1/1 Running 0 38h harbor-harbor-jobservice.

oc get pods -n guestbook-project Copy the name of one of the new pods and use oc describe pod to confirm that the pod is using the v2 image like the following screenshot: oc describe pod <pod-name> Notice that the service and router objects remain unchanged when you change the underlying Docker image version of your pod Here is the command with some example output of what to expect: # oc get pod --all-namespaces -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE my-project my-pod-43-d9mo6 1/1 Running 0 1d 192.168..183 node3.krenger.local yet-another-project another-pod-43-7g3r0 1/1 Running 0 2d 192.168..184 node4.krenger.local [.. When the Kubernetes system is running correctly, each of the pods should have: In the READY column all pods should be counted - for example, 1/1 or 3/3. A value of Running in the STATUS column. A STATUS value other than Running indicates an issue with the Kubernetes infrastructure Common commands oc status oc logs pod <mypod> oc get pods --all-namespaces oc describe pod <mypod> oc get services --sort-by=.metadata.name oc delete all -l app=tomcat oc delete pod <mypod> --grace-period=0 oc export bc,dc,is,svc --as-template=myapp.yam kubectl get pods --field-selector status.phase=Running Note: Field selectors are essentially resource filters. By default, no selectors/filters are applied, meaning that all resources of the specified type are selected. This makes the kubectl queries kubectl get pods and kubectl get pods --field-selector equivalent

Chapter 1. Working with pods OpenShift Container Platform ..

$ oc get pods NAME READY STATUS RESTARTS AGE hive-metastore-presto-odh-5fd66d5848-w84cw 1/1 Running 0 6m46s postgres-68d5445b7c-fpp8x 1/1 Running 0 13m presto-coordinator-presto-odh-84cf47f6f9. $ oc get pods NAME READY STATUS RESTARTS AGE vault-0 1/1 Running 0 45s vault-agent-injector-777b86fbbd-cxrgb 1/1 Running 0 45s The vault-0 pod runs a Vault server in development mode. The vault-agent-injector pod performs the injection based on the annotations present or patched on a deployment You can also check the status in the terminal by running $ oc get pods. Figure: Scaling a deployment up to three pods using the OCP web console. 2. After the pods are up and running, run $ oc exec -it <pod_2_name> -c <container_name> -- powershell.exe again but with a new pod that was just deployed after scaling. 3 $ oc get pods NAME READY STATUS RESTARTS AGE kindhermann 2/2 Running 0 39s $ oc get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kindhermann NodePort 172.30.103.100 <none> 80:30579/TCP 45s Kubernetes ClusterIP 172.30..1 <none> 443/TCP 44m openshift ExternalName <none> Kubernetes.default.svc.cluster.local <none> 36 $ oc version oc v1.1.3 kubernetes v1.2.0-origin $ oc get pods NAME READY STATUS RESTARTS AGE docker-registry-1-yc9e8 1/1 Running 1 6d router-1-mm44t 1/1 Running 4 6d If you're familiar with Kubernetes, you'll probably recognize the last command as the output from kubectl

Investigating pod issues - Troubleshooting Support

  1. Get all the pods within the default namespace. The Consul client and server pods are displayed here prefixed with consul.You should see 1x consul-server pods and N consul pods, where N is the number of worker nodes in the cluster.. Wait until the server and client pods report that they are Running and ready (1/1). $ oc get pods-n default NAME READY STATUS RESTARTS AGE consul-consul-2llf7 1 / 1.
  2. And wait for the PODs up&running [root@utility ~]# oc get pod -n openshift-storage NAME READY STATUS RESTARTS AGE noobaa-operator-85d86479fc-n8vp5 1/1 Running 0 106s ocs-operator-65cf57b98b-rk48c 1/1 Running 0 106
  3. Personal website of Simon Krenger. So in any larger container orchestrator installation, be it Kubernetes or OpenShift, you will encounter pods that crash regularly and enter the CrashLoopBackOff status. $ oc get pod --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE [..] my-project-1 helloworld-11-9w3ud 1/1 Running 0 7h my-project-2 myapp-simon-43-7macd 0/1 CrashLoopBackOff 3774 9

To test that your pod is up and running, execute this command and wait until the status is Running: $ oc get pods --watch NAME READY STATUS RESTARTS AGE hello-world 1/1 Running 0 30s Next steps. Azure Container Registry; Quickstart: Create a private container registry using the Azure CL oc get pods. Navigate to the <install_dir>/tools. Run the following command to get the status of all the pods: oc get pods. Ensure that the status of all the pods is Running. Validate the Rehydration. After you have completed performing all the tasks mentioned in this section, you can validate if the rehydration was successful.. # oc get pods -n openshift-storage NAME READY STATUS RESTARTS AGE noobaa-operator-7c78fd8589-c9rt6 1/1 Running 0 96s ocs-metrics-exporter-844cd5988b-khg7b 1/1 Running 0 95s ocs-operator-7dcc6dc48f-4kzjw 1/1 Running 0 96s rook-ceph-operator-5c98f687bc-gdd4l 1/1 Running 0 96

Let's verify the number of pods with the oc get pods command: oc get pods NAME READY STATUS RESTARTS AGE parksmap-65c4f8b676-fxcrq 1/1 Running 0 92s parksmap-65c4f8b676-k5gkk 1/1 Running 0 24

Openshift 3.x Pod Stuck in Pending Status Due to no Nodes ..

If you have one or two pods to delete, you can easily do that, by first running the kubectl get pod command: kubectl get pod -n studytonight. NAME READY STATUS RESTARTS AGE. busybox-h6yw8 1/1 Running 0 1h. nginx-07rdsz 0/1 Evicted 8 16m. busybox-fzr9h 0/1 Evicted 8 16m. Then using the pod name to delete the pod, like: kubectl delete pod nginx. $ oc get pod -n openshift-image-registry NAME READY STATUS RESTARTS AGE cluster-image-registry-operator-674b759cfb-vvsmr 2/2 Running 0 41d image-pruner-1600387200-5qzgn 0/1 Completed 0 2d10h image-pruner-1600473600-x8rd6 0/1 Completed 0 34h image-pruner-1600560000-ss6mn 0/1 Completed 0 10h image-registry-6f4b4db789-2wdmt 1/1 Running 0 41d node. The following output is a sample of an execution of oc get pods: NAME READY STATUS RESTARTS AGE docker-registry-1-5r583 1/1 Running 0 1h Chapter3.Executing Commands 118 DO280-OSE3.-en-2-20160126 trainingrouter-1-l44m7 1/1 Running 0 1h oc get all Additionally, if the administrators wants a summary of all of the most important components of the. By using the oc commands, you can see that the security pod is in Pending state: $ oc get pods --namespace samplens -l release=build-sample && oc get pods --namespace samplens -l release=sample NAME READY STATUS RESTARTS AGE build-sample-build- 1/1 Running 0 1h build-sample-builder-40 1/1 Running 0 1h NAME READY STATUS RESTARTS AGE sample.

Although it is a pod, it is a special kind of pod. Once the pod is launched, you can open a second terminal window and run oc get pods and find the corresponding pod named node-name-debug and use oc get -o yaml podName to display its YAML output. Observe the output We can watch the deployment progress until we see our application running: oc get pods -w. Should provide a listing: NAME READY STATUS RESTARTS AGE baeldung-db-1-9m2cr 1/1 Running 1 1h spring-boot-bootstrap-1-x6wj5 1/1 Running 0 46s Before we test the application, we need to determine the route: oc get routes. Will print the routes in the. Here is a comprehensive Openshift Container Platform cheatsheet for Developers/Administrators.. Openshift Container Platform Login and Configuration # with a user oc https://192.168.99.100:8443 -u developer -p developer # as system admin oc -u system:admin #User Information oc whoami #View your configuration oc config view #Update the current context to have users . $ oc status In project test-project on server https://127.0.0.1:8443 svc/deployment-example - 172.30.15.201:8080 dc/deployment-example deploys istag/deployment-example:latest deployment #1 deployed about a minute ago - 1 pod 2 infos identified, use 'oc status --suggest' to see details. 6. Get service detailed information

List down our pods again. $ oc get pods NAME READY STATUS RESTARTS AGE mongo-db-dev- 2/2 Running 0 20h mongo-db-build 0/1 Completed 0 18h mynew-app-1-build 0/1 Terminating 0 7d . It's gone !!! Do the same for that mynew-app-1-build as well $ oc get pods NAME READY STATUS RESTARTS AGE ibm-mf-defaultsecrets-job-7z42m 0/1 Completed 0 5m21s ibm-mf-push-77fb65c758-wtg28 0/1 Running 0 5m16s ibm-mf-server-d87ddf67f-x9n4x 0/1 Running 0 5m16s Check if the Database that Mobile Foundation is connected to is reachable or not oc get pods You should an output similar to the following: NAME READY STATUS RESTARTS AGE parksmap-65c4f8b676-fxcrq 1/1 Running 0 52 Once the playbook has finished, you can check that the CSI pods are operational and that storage class has been created. oc get pods -n kube-system NAME READY STATUS RESTARTS AGE vsphere-csi-controller- 5/5 Running 0 90m vsphere-csi-node-9b4sf 3/3 Running 0 90m vsphere-csi-node-dqht2 3/3 Running 0 90

oc get deploy Verify the ReplicaSet has been created: oc get replicaset Verify the pods are running: oc get pods Attempt to delete the Deployment. oc delete deployment finalizer-test Open up another terminal by clicking the + button and select Open New Terminal Open a terminal, and using the 'oc' command to your OpenShift cluster, and list the pods in the open-cluster-management namespace. <hub cluster console> $ watch -n 1 oc get pods -n open-cluster-management. When all pods get into a 'Running' state, get the RHACM route so you will be able to log into the RHACM console $ oc get pods NAME READY STATUS RESTARTS AGE sso-1-deploy 0/1 Completed 0 10m sso-postgresql-1-deploy 0/1 Completed 0 10m sso-postgresql-1-fzgf7 1/1 Running 0 3m46s When the sso-postgresql pod starts correctly, it provides the following log output This will create NFD pods in the openshift-nfd namespace that poll the OpenShift nodes for hardware resources and catalogue them. After a successful build, verify that a NFD pod is running on each nodes. $ oc get pods -n openshift-nfd NAME READY STATUS RESTARTS AGE nfd-master-mc99f 1/1 Running 0 51s nfd-master-t7rrl 1/1 Running 0 51s nfd-master.

You can verify the POD in running state either via CLI or in the GUI as shown below. 2 NAME READY STATUS RESTARTS AGE. 3 nfs-pod-provisioner-8458 # oc get pods $ oc get pods NAME READY STATUS RESTARTS AGE database-1-le4wx 1/1 Running 0 1m frontend-1-e572n 1/1 Running 0 27s frontend-1-votq4 1/1 Running 0 31s opeshift-sample-build-1-build 0/1 Completed 0 1m We can check if the application services are created as per the service definition usin Rahil Maknojia. 25 Feb 2018 • 1 min read. To check status of a pod in kubernetes cluster. Connect to master node and execute below command. Below command will give status of all pods from default namespace. kubectl get pods. If you like to check the status of pods in system namespace, execute below command. kubectl get pods --all-namespaces OpenShift is a platform as a service product from Red Hat. The software that runs the service is open-sourced under the name OpenShift Origin, and is available on GitHub. OpenShift v3 is a layered system designed to expose underlying Docker and Kubernetes concepts as accurately as possible, with a focus Continue readin $ oc new-app --name nginx-app --docker-image=nginx $ oc get deployment NAME READY UP-TO-DATE AVAILABLE AGE nginx-app 1/1 1 1 2m2s $ oc get pods NAME READY STATUS RESTARTS AGE nginx-app-6d7c86dfd7-b6mvz 1/1 Running 0 2m4s $ $ oc expose service nginx-app route.route.openshift.io/nginx-app exposed $ oc get route NAME HOST/PORT PATH SERVICES PORT.

The system microservice returns the JVM system properties of the running container. It also returns the pod name in the HTTP header, which makes pod replicas more distinguishable from each other. run the following command to check the status of your pods: oc get pods $ oc get pods NAME READY STATUS RESTARTS AGE mysql-1-2fzj2 1/1 Running 0 2m Now let's forward this pod through the port 3306 as follows: $ oc port-forward mysql-1-2fzj2 3306:3306 Forwarding from 127.0.0.1:3306 -> 3306 Forwarding from [::1]:3306 -> 3306 Handling connection for 3306 Great oc new-project azfiletest oc new-app httpd-example #Wait for the pod to become Ready curl $(oc get route httpd-example -n azfiletest -o jsonpath={.spec.host}) #If you have set the storage class by default, you can omit the --claim-class parameter oc set volume dc/httpd-example --add --name=v1 -t pvc --claim-size=1G -m /data --claim-class='azure-file' #Wait for the new deployment to rollout.

How to filter a specific pod from the oc get pods list

mgrayson @ Michaels-MBP percona-server-mongodb-operator % oc get pods NAME READY STATUS RESTARTS AGE my - cluster - name - cfg - 0 2 / 2 Running 0 51 Kubectl supports JSONPath template. JSONPath template is composed of JSONPath expressions enclosed by curly braces {}. Kubectl uses JSONPath expressions to filter on specific fields in the JSON object and format the output. In addition to the original JSONPath template syntax, the following functions and syntax are valid: Use double quotes to quote text inside JSONPath expressions $ oc get pods NAME READY STATUS RESTARTS AGE galera-ansible-operator-bc6cd548-46b2r 1/1 Running 5 30m galera-node-0001 1/1 Running 0 26m galera-node-0002 0/1 Running 0 1m galera-node-0003 0/1 Running 0 56s. And after about a minute (each Galera node has to start and sync data from another member), we see the new pods become ready: $ oc get pods $ oc get pods -l app=cassandra NAME READY STATUS RESTARTS AGE cassandra-0 1/1 Running 0 2m cassandra-1 1/1 Running 0 1m cassandra-2 1/1 Running 1 43s Let's also check if persistent volume claims are bound to the volumes [root@e26-linuxjb ocp-install2]# oc get pods NAME READY STATUS RESTARTS AGE djangotodo-1-build 0/1 Completed 0 41m djangotodo-8f66c4754-gzhj2 1/1 Running 0 30m. Once the POD is ready, expose the service to the outside world by executing the following command

1. SSH into node 2. touch /var/run/ovs-config-executed 3. Delete ovs-* pod on the node, verify that it restarts and says something like openvswitch is running in systmed 4. systemctl start ovs-configuration (this starts all dependent ovs services as well) Comment 4 Robert Bost 2020-12-01 22:56:10 UTC Check all pods are up and running: oc get pods NAME READY STATUS RESTARTS AGE mariadb-1-deploy 0/1 Completed 0 3m34s mariadb-1-svkzh 1/1 Running 0 3m29s wordpress-1-build 0/1 Completed 0 2m21s wordpress-754b56ffc7-rjz2g 1/1 Running 0 67s. With the route you created, navigate to http. oc get pods NAME READY STATUS RESTARTS AGE root-app-1-lljqm 0/1 CrashLoopBackOff 1 5s Show more The pod log shows that the delete command failed to execute on OpenShift Container Platform because its default settings don't allow processes with root access to run inside an image

Bug 1814457: fix (catsrc): remove limits on catalogsource pods. 2021-01-20 21:13:15 UTC. Red Hat Product Errata. RHBA-2020:2409 During the execution of CronJob, the automatically created pods will debug on nodes for backup execution. With these commands, you can check the pods that were created for a backup running: $ oc get pods -n ocp-etcd-backup. NAME READY STATUS RESTARTS AGE. pod/backup-jcn87 1/1 Running 0 40s After some minutes of the Keycloak deployment, we can check things up by controlling the number of pods running into our project: $ oc get pods -n fruits-catalog NAME READY STATUS RESTARTS AGE fruits-catalog-1-xx7nd 1/1 Running 0 2h fruits-catalog-s2i-1-build 0/1 Completed 0 2h mongodb-1-t85wm 1/1 Running 0 2h keycloak-649b794bf-x9xp9 1/1. You can also verify the Pods status using the following command: oc get pods. Output: NAME READY STATUS RESTARTS AGE deployment-example-1-b9prf 1/1 Running 0 2m Now, expose the application for external access using the following command: oc expose service/deployment-example. Output $ oc get project. CODE. Example output: oc -n appdynamics get pods. CODE. Example output: NAME READY STATUS RESTARTS AGE appdynamics-operator-95ffb549c-m8tjv 1/1 Running 0 30s. CODE. This output shows that OpenShift extends the custom resource definitions that you provided

kubernetes - How to get status of a particular pod or

Check if the strimzi-cluster-operator is in Ready status. oc get pods -n kafka external-kafka and external-entity-operator pods are ready and running. oc get pods -n kafk List the AWS EBS driver pods in the kube-system namespace and verify that the status is Running. Note that it might take a few minutes for the storage request to be fulfilled and for your app to get into a Running state. oc get pods oc get pods -n kube-system | greb ebs.

Video: `oc get pods --show-all=false -o name` doesn't work

How To Check Pod / Container Metrics on OpenShift

# oc get pods -n sysbench -w Example output: NAME READY STATUS RESTARTS AGE sysbench-file-write-m6mnd 0/1 ContainerCreating 0 26s sysbench-file-write-m6mnd 1/1 Running 0 27s sysbench-file-write-m6mnd 0/1 Completed 0 41 $ oc get all -n gpu-operator-resources //Output NAME READY STATUS RESTARTS AGE pod/nvidia-container-toolkit-daemonset-sgr7h 1/1 Running 0 160m pod/nvidia-dcgm-exporter-twjx4 2/2 Running 0 153m pod/nvidia-device-plugin-daemonset-6tbfv 1/1 Running 0 156m pod/nvidia-device-plugin-validation 0/1 Completed 0 156m pod/nvidia-driver-daemonset-m7mwk 1.

Create, scale, upgrade, and rollback an application on Red

$ oc get pods NAME READY STATUS RESTARTS AGE configmapcontroller-1-397qh 1/1 Running 3 5 $ oc get pods NAME READY STATUS RESTARTS AGE camel-cloud-svc-1-deploy 1/1 Running 0 27s camel-cloud-svc-1-ojyy6 0/1 Running 0 24s camel-cloud-svc-1-sbkbi 0/1 Running 0 24s camel-cloud-svc-s2i-2-build 0/1 Completed 0 55 oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.-.nightly-2020-03-26-010528 True False 52m Cluster version is 4.4.-.nightly-2020-03-26-010528 Show events ordered by timestamp oc get event --sort-by=.metadata.creationTimestam [email protected]:~# kubectl get pod NAME READY STATUS RESTARTS AGE my-dep-557548758d-kz6r7 1/1 Running 0 11m my-dep-557548758d-svg7w 1/1 Running 0 11m. Get the deployment information: [email protected]:~# kubectl get deployments NAME READY UP-TO-DATE AVAILABLE AGE my-dep 2/2 2 2 12m. Now, set the replica number to zero: [email protected.

OpenShift: List all pods in cluster - Simon Krenge

$ oc get pods NAME READY STATUS RESTARTS AGE postgresql-5-sbfm5 1/1 Running 0 27d simple-cron-1536609780-fmrhf 0/1 ContainerCreating 0 1s simple-mpq8h 0/1 Completed 0 26d To view logs of one of the scheduled job executions, passing the appropriate pod name oc get csv -n openshift-storage Example output. NAME DISPLAY VERSION REPLACES PHASE ocs-operator.v4.6. OpenShift Container Storage 4.6.0 ocs-operator.v4.5.2 Succeede By pod name:. How to wait for a Kubernetes pod to be ready — one liner is published by Reuven Harrison

云原生存储:打造被OpenShift纳管的Ceph上:Ceph学习系列11_大魏分享-Lambda在线

Checking Kubernetes services status - PowerAI Vision

It uses the OpenShift Client tool (oc) to pull the runtime metrics every 30 seconds or so for the duration of the test and stores it in a set of simple CSV files, one for nodes and one for each monitored pod. I start the script in the background before the user provisioning starts in order to catch the before state, and leave the script. Running of privileged containers. [alex @freddy ~] $ oc get pods. 2. NAME READY STATUS RESTARTS AGE. 3. wordpress-2-8 vxn2 1 / 1 Running 0 50 s. 4 [alex @freddy ~]. The oc get command allows you to display details about resource objects. When run, it will display a set of default fields for that resource type. You can use a label selector to restrict the query to a set of resource objects. $ oc get pods --selector app=training NAME READY STATUS RESTARTS AGE training-22-g67cv 1/1 Running 0 1h training. $ oc get pods -l application=default-interconnect NAME READY STATUS RESTARTS AGE default-interconnect-7458fd4d69-bgzfb 1/1 Running 0 6d21h Connect to the pod and run the qdstat --connections command to list the known connections Validate the pod status and mount point: [core@csah ~]$ oc get pods. NAME READY STATUS RESTARTS AGE. unitypod 1/1 Running 0 31m [core@csah ~]$ oc exec -it unitypod -- df -h /var/www/html. Filesystem Size Used Avail Use% Mounted on /dev/sdc 20G 45M 20G 1% /var/www/htm

oc Cheat Sheet · OpenShift in Action - liveBook · Mannin

Run the following command to check the status of the pods: kubectl get -n<your project name> pods . 7) Verify you can use the filter options now . 8) (Optional) You can safely delete all the evicted pods (if any available): for evicted in $(kubectl get pods | grep Evicted | awk '{print $1}'); do kubectl delete pod ${evicted}; don The process is complete when all Pods have reached their Running status. You can check it with the following command: $ oc get pods The result should look as follows

Application Migration using Transformation Advisor andHow to Run HA Kafka on Red Hat OpenShift - PortworxTake a Dip into Windows Containers with OpenShift 4

Pre-req: Switch to rook-ceph namespace with oc project rook-ceph. Ensure ceph-mgr pod is Running. oc get pods -l app=rook-ceph-mgr. NAME READY STATUS RESTARTS AGE rook-ceph-mgr 1/1 Running 0 14h. Ensure service monitor is present. oc get servicemonitor rook-ceph-mgr. NAME AGE rook-ceph-mgr 14h. Ensure prometheus rules are present Standalone mode is perfect when running Kuma in a single cluster across one environment. It may take a while for OpenShift to start the Kuma resources, you can check the status by executing: $ oc get pod -n kuma-system 1 # 3. Use Kuma. Kuma. We assume you have a cluster running and you have already logged into it. $ oc get pods NAME READY STATUS RESTARTS AGE wildfly-clustering-demo-3-9dmrk 1/1 Running 0 117s wildfly-clustering-demo-3-deploy 0/1 Completed 0 3m6s wildfly-clustering-demo-3-f99qb 1/1 Running 0 3m2s wildfly-clustering-demo-3-snh74 1/1 Running 0 117s wildfly. $ oc get all NAME READY STATUS RESTARTS AGE pod / keystone-db-init-1-build 1 / 1 Running 0 2m55s NAME REVISION DESIRED CURRENT TRIGGERED BY deploymentconfig.apps.openshift.io / keystone-db-init 0 1 0 config,image (keystone-db-init:latest) NAME TYPE FROM LATEST buildconfig.build.openshift.io / keystone-db-init Docker Git @ chmodconf 1 NAME TYPE. Let's have a look at the pods: kubectl get pod -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES server-1-deploy 0/1 Completed 0 54m 10.131..32 aro2-p8bjm-worker-northeurope1-qt8l7 <none> <none> server-1-ppl25 1/1 Running 0 54m 10.128.2.24 aro2-p8bjm-worker-northeurope3-wl4vw <none> <none> sqlapi-1-8jgx8 1/1.