I believe this is going to be an installer issue. As of 3.9, the web console is deployed in its own pod externally. If the operator doesn't want a web console, the web console shouldn't be deployed. The disabledFeature=WebConsole flag is no longer used.

The registry deployment type should do whatever is necessary to prevent the deployment of the web console.

Sam,

Lets drop something like this at the end of playbooks/init/basic_facts.yml this will depend on the earlier call to sanitize inventory which migrates from the legacy 'deployment_subtype' that QE is setting to 'openshift_deployment_subtype'.

- name: Disable web console if required
  hosts: oo_masters_to_config
  gather_facts: no
  tasks:
  - set_fact:
      openshift_web_console_install: False
    when: 
    - openshift_deployment_subtype == 'registry'

BTW, according to comment 1, if the disabledFeature=WebConsole flag is no longer used, it is better to be removed from /etc/origin/master/master-config.yaml either.

https://github.com/openshift/openshift-ansible/pull/6927

Verified this bug with openshift-ansible-3.9.0-0.36.0.git.0.da68f13.el7.noarch, and PASS.

When deployment_subtype=registry is set, no web console is installed.
# oc get project openshift-web-console
Error from server (NotFound): namespaces "openshift-web-console" not found