Autoscaling for Memory Utilization is not working as expected. creating HPA for Memory based autoscaling is failing while looking for resource.

Version-Release number of selected component (if applicable):
$ oc version
oc v4.0.0-0.101.0
kubernetes v1.11.0+0e214b3455
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://10.1.10.122:6443
kubernetes v1.13.4+a469c28
[nathan@dhcp-140-7 0508]$ oc get clusterverion
error: the server doesn't have a resource type "clusterverion"
[nathan@dhcp-140-7 0508]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE     STATUS
version   4.1.0-0.nightly-2019-05-07-233329   True        False         6h52m     Cluster version is 4.1.0-0.nightly-2019-05-07-233329


How reproducible:
Always

Steps to Reproduce:

make sure autoscaling/v2beta1 available
$ oc get --raw /apis/autoscaling/v2beta1
{"kind":"APIResourceList","apiVersion":"v1","groupVersion":"autoscaling/v2beta1","resources":[{"name":"horizontalpodautoscalers","singularName":"","namespaced":true,"kind":"HorizontalPodAutoscaler","verbs":["create","delete","deletecollection","get","list","patch","update","watch"],"shortNames":["hpa"],"categories":["all"]},{"name":"horizontalpodautoscalers/status","singularName":"","namespaced":true,"kind":"HorizontalPodAutoscaler","verbs":["get","patch","update"]}]}


1. Deploy app
~~~
# oc get dc,pods
NAME                                         REVISION   DESIRED   CURRENT   TRIGGERED BY
deploymentconfig.apps.openshift.io/ruby-ex   1          1         1         config,image(ruby-ex:latest)

NAME                  READY     STATUS      RESTARTS   AGE
pod/ruby-ex-1-6kt4v   1/1       Running     0          2d
pod/ruby-ex-1-build   0/1       Completed   0          2d
~~~

2. Create the HPA config file:
~~~
# cat hpa.yaml 
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: hpa-resource-metrics-memory 
spec:
  scaleTargetRef:
    apiVersion: apps/v1 
    kind: DepoymentConfig 
    name: ruby-ex
  minReplicas: 1 
  maxReplicas: 10 
  metrics:
  - type: Resource
    resource:
      name: memory
      targetAverageUtilization: 50 
~~~

3. Create the autoscale:
~~~
[nathan@dhcp-140-7 0508]$ oc create -f hpa.yaml 
horizontalpodautoscaler.autoscaling/hpa-resource-metrics-memory created
[nathan@dhcp-140-7 0508]$ oc describe hpa 
Name:                                                     hpa-resource-metrics-memory
Namespace:                                                weinliu
Labels:                                                   <none>
Annotations:                                              <none>
CreationTimestamp:                                        Wed, 08 May 2019 18:45:13 +0800
Reference:                                                DepoymentConfig/ruby-ex
Metrics:                                                  ( current / target )
  resource memory on pods  (as a percentage of request):  <unknown> / 50%
Min replicas:                                             1
Max replicas:                                             10
DepoymentConfig pods:                                     0 current / 0 desired
Conditions:
  Type         Status  Reason          Message
  ----         ------  ------          -------
  AbleToScale  False   FailedGetScale  the HPA controller was unable to get the target's current scale: no matches for kind "DepoymentConfig" in group "apps"
Events:
  Type     Reason          Age   From                       Message
  ----     ------          ----  ----                       -------
  Warning  FailedGetScale  1s    horizontal-pod-autoscaler  no matches for kind "DepoymentConfig" in group "apps"


Name:                        resource-memory
Namespace:                   weinliu
Labels:                      <none>
Annotations:                 <none>
CreationTimestamp:           Wed, 08 May 2019 18:16:33 +0800
Reference:                   ReplicationController/hello-openshift
Metrics:                     ( current / target )
  resource memory on pods:   <unknown> / 500Mi
Min replicas:                1
Max replicas:                10
ReplicationController pods:  0 current / 1 desired
Conditions:
  Type         Status  Reason            Message
  ----         ------  ------            -------
  AbleToScale  True    SucceededRescale  the HPA controller was able to update the target scale to 1
Events:
  Type    Reason             Age                 From                       Message
  ----    ------             ----                ----                       -------
  Normal  SuccessfulRescale  3m (x101 over 28m)  horizontal-pod-autoscaler  New size: 1; reason: Current number of replicas below Spec.MinReplicas
~~~

4. Check what apiVersion is HPA created:
~~~[nathan@dhcp-140-7 0508]$ oc get hpa -o yaml hpa-resource-metrics-memory
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
  annotations:
    autoscaling.alpha.kubernetes.io/conditions: '[{"type":"AbleToScale","status":"False","lastTransitionTime":"2019-05-08T10:45:28Z","reason":"FailedGetScale","message":"the
      HPA controller was unable to get the target''s current scale: no matches for
      kind \"DepoymentConfig\" in group \"apps\""}]'
    autoscaling.alpha.kubernetes.io/metrics: '[{"type":"Resource","resource":{"name":"memory","targetAverageUtilization":50}}]'
  creationTimestamp: 2019-05-08T10:45:13Z
  name: hpa-resource-metrics-memory
  namespace: weinliu
  resourceVersion: "162589"
  selfLink: /apis/autoscaling/v1/namespaces/weinliu/horizontalpodautoscalers/hpa-resource-metrics-memory
  uid: 5c3bddf4-717e-11e9-aa80-801844ef10ac
spec:
  maxReplicas: 10
  minReplicas: 1
  scaleTargetRef:
    apiVersion: apps/v1
    kind: DepoymentConfig
    name: ruby-ex
status:
  currentReplicas: 0
  desiredReplicas: 0
~~~

from the 2 and 4 we can see that the apiVersion of the resources are getting changes. 


Actual results:
The HPA is failing.

Expected results:
The pods should be able to autoscale based on the Memory utilization.

Additional Info
The same issue on 3.11 is still new
https://bugzilla.redhat.com/show_bug.cgi?id=1701469