If you are not familiar with the oc command, refer to OpenShift - Getting Started with the oc command.

When deploying an application using the oc new-app command, if the --as-deployment-config flag is not used, the application will be created as a deployment, not a deployment config. In this scenario, the oc get deployments command would be used to list the deployments. On the other hand, if the --as-deployment-config flag is used, the application will be created as a deployment config. In this scenario, the oc get deploymentconfigs command would be used.

When deploying an application using the oc new-app command, if the --as-deployment-config flag is not used, the application will be created as a deployment, not a deployment config. In this scenario, a replica set will be used to create the pods.

If the --as-deployment-config flag is used, the application will be created as a deployment config. In this scenario, a replication controller will be used to create the pods.

The oc get deploymentconfigs (or oc get dc) command can be used to list the deployment configs in a namespace.

TIP

The -A or --all-namespaces flag can be used to list the deployment configs in every namespace.

The -n or --namespace flag can be used to list the deployment configs in a certain namespace.

~]$ oc get deploymentconfigs
NAME      REVISION   DESIRED   CURRENT   TRIGGERED BY
my-app    1          1         1         config,image(my-app:latest)