openshift-state-metrics has logic to generate metrics for deploymentconfigs.  That logic will fail when the deploymentconfig capability is disabled and the api does not exist.

see:
https://github.com/openshift/openshift-state-metrics/blob/774cb2ff4b9e21c452650643528c6fa190c7885a/main.go#L65-L70

https://github.com/openshift/openshift-state-metrics/blob/774cb2ff4b9e21c452650643528c6fa190c7885a/pkg/collectors/deployment_config.go#L214-L242

4.14

always

1.  oc logs -c openshift-state-metrics openshift-state-metrics-8d8965fc7-r6kcz -n openshift-monitoring | grep deployment

errors in the openshift state metrics container logs due to non-existent api endpoint

E1012 01:37:32.636894       1 reflector.go:138] github.com/openshift/openshift-state-metrics/pkg/collectors/builder.go:228: Failed to watch *v1.DeploymentConfig: failed to list *v1.DeploymentConfig: the server could not find the requested resource (get deploymentconfigs.apps.openshift.io)

no errors in the log related to the missing deploymentconfig api