Kubernetes Deploymentconfig vs Deployment

 

DeploymentConfig objects involve one or more replication controllers, which contain a point-in-time record of the state of a deployment as a pod template.

To create deploymentconfig using image:

oc create deploymentconfig apache-dc --image=httpd

To view ReplicaController

oc get rc

deploymentconfig → replicationcontroller → pod

A replication controller ensures that a specified number of replicas of a pod are running at all times. If pods exit or are deleted, the replication controller acts to instantiate more up to the defined number.

The replication controller does not perform auto-scaling based on load or traffic, as it does not track either.

 

Deployment objects involve one or more replica sets, a successor of replication controllers.

oc create deployment d1 --image=httpd

oc get deploy

Deployment also create replicaset

oc get rs

deployment → replicaset → pod

ReplicaSet is a native Kubernetes API object that ensures a specified number of pod replicas are running at any given time

 

Deployment and DeploymentConfig objects is the properties of the CAP theorem that each design has chosen for the rollout process. DeploymentConfig objects prefer consistency, whereas Deployments objects take availability over consistency.

 

deployments do not support automatically rolling back to the last successfully deployed replica set in case of a failure.

Deployments do not support user-specified custom deployment strategies yet