Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3867

"oc new-app" deployment config behavior

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • openshift-4.10.z
    • oc
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%
    • Red Hat OpenShift Container Platform

      1. Proposed title of this feature request

      oc new-app to fill in image name in the Deployment obj upon creation

       

      2. What is the nature and description of the request?

      When oc new-app creates the Deployment object, it leave the image field empty and sets an annotation so it gets filled in after the Build completes. This behaviour is not compatible with previous versions of OpenShift (before 4.5, including 3.11 with DeploymentConfig).

       

      The expected default behaviour  of oc new-app should be to maintain backwards compatibility and fill in the image name in the creation of the Deployment object.

       

      3. Why does the customer need this? 

      Customer is going through migration from OCP 3.11 to ROSA/ARO and this is forcing them to avoid using Deployment and remain generating DeploymentConfig, creating unnecessary technical debt and most likely increased burden on Red Hat to continue supporting DeploymentConfig on OpenShift v4.

       

      4. List any affected packages or components.

      oc-cli , oc new-app

       

            gausingh@redhat.com Gaurav Singh
            rhn-support-akadanna Archith Kadanna Palli
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: