rhbofa
Cadet
Cadet
  • 1,769 Views

When to user as-deployment-config while running oc new-app

Jump to solution

Hi,

I'm confused when to use 'as-deployment-config' while running oc new-app. Can anyone please help?

 

Thanks.

Labels (1)
0 Kudos
1 Solution

Accepted Solutions
flozano
Moderator
Moderator
  • 1,714 Views

Since OpenShift 3.0, many years ago, the oc new-app command creates DeploymentConfig resources which are an OpenShift-only API extension to Kubernetes. At that time, Kubernetes didn't had its workloads API -- there were no Deployments, Jobs, CronJobs, StatefulSets, nor DaemonSets. There where only Pods and ReplicationControllers.

Since them Kubernets evolved, with lots of contributions from Red Hat, but sometimes an open source community doesn't take contributions unchanged. So a while ago Kubernetes got the Deployment resource that is similar but different than DeploymentConfig.

Red Hat is NOT about creating forks nor "open core" but about hardening, integrating, and supporting open source software, and because of that OpenShift 4.5 switched to use Deployment resources by default. The --as-deployment-config switch just reverts to the old behavior.

View solution in original post

0 Kudos
3 Replies
Alexandre
Starfighter Starfighter
Starfighter
  • 1,764 Views

Hi

May be this documentation article fhelp you understend the difference:

https://docs.openshift.com/container-platform/4.5/applications/deployments/what-deployments-are.html...

0 Kudos
flozano
Moderator
Moderator
  • 1,715 Views

Since OpenShift 3.0, many years ago, the oc new-app command creates DeploymentConfig resources which are an OpenShift-only API extension to Kubernetes. At that time, Kubernetes didn't had its workloads API -- there were no Deployments, Jobs, CronJobs, StatefulSets, nor DaemonSets. There where only Pods and ReplicationControllers.

Since them Kubernets evolved, with lots of contributions from Red Hat, but sometimes an open source community doesn't take contributions unchanged. So a while ago Kubernetes got the Deployment resource that is similar but different than DeploymentConfig.

Red Hat is NOT about creating forks nor "open core" but about hardening, integrating, and supporting open source software, and because of that OpenShift 4.5 switched to use Deployment resources by default. The --as-deployment-config switch just reverts to the old behavior.

0 Kudos
rhbofa
Cadet
Cadet
  • 1,695 Views

Thanks for the explanation. Now it makes sense. 

0 Kudos
Join the discussion
You must log in to join this conversation.