Uploaded image for project: 'OpenShift Workloads'
  1. OpenShift Workloads
  2. WRKLDS-636

Deprecation of DeploymentConfigs in OpenShift

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • 4.14
    • 4.13
    • Workloads Sprint 230, Workloads Sprint 231, Workloads Sprint 232, Workloads Sprint 233, Workloads Sprint 234, Workloads Sprint 235, Workloads Sprint 236, Workloads Sprint 237, Workloads Sprint 238, Workloads Sprint 239, Workloads Sprint 240

      We need some official statement we can show customers in case they request a feature instead of “oh, I am sorry, we have decided internally we no longer do that”. The same for fixing bugs. What’s the line between a missing feature and a bug (see https://issues.redhat.com/browse/OCPBUGS-3805)

      *TODO*

      • Measure how many deploymentconfigs are in the fleet
      • Measure how many custom deploymentconfigs are in the fleet
      • Jan to learn about the imagestream injection code for workload resources. See https://docs.openshift.com/container-platform/4.11/openshift_images/using-imagestreams-with-kube-resources.html
      • Clarify that we are not adding new features to deploymentconfigs. Use init containers.
      • Having deployer pod tolerations match the workload toleration is not desired behavior since deployer pods are orchestration pods which are likely to logically have different node targets. Changing this behavior is not a goal.

      DC metrics are defined under https://github.com/openshift/openshift-controller-manager/blob/master/pkg/apps/metrics/prometheus/metrics.go#L27

            jchaloup@redhat.com Jan Chaloupka
            jchaloup@redhat.com Jan Chaloupka
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: