I edited the config file. to point to the singularity socket and set
  - node-role.kubernetes.io/compute=true,runtime=singularity

then i ran
# openshift-node --config /etc/origin/node/node-config.yaml

It looks good

[root@ip-172-16-241-23 ~]# oc get node
NAME                             STATUS    ROLES     AGE       VERSION
ip-172-16-21-199.ec2.internal    Ready     infra     16h       v1.11.0+d4cacc0
ip-172-16-241-23.ec2.internal    Ready     master    16h       v1.11.0+d4cacc0
ip-172-16-247-101.ec2.internal   Ready     compute   16h       v1.11.0+d4cacc0

The crio configs weren't reverted in the config file. and the startup points to singulartiy.sock

W0613 12:13:17.635619   23496 util_unix.go:75] Using "/var/run/singularity.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/singularity.sock".
W0613 12:13:17.635718   23496 util_unix.go:75] Using "/var/run/singularity.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/singularity.sock".
I0613 12:13:17.685173   23496 kuberuntime_manager.go:186] Container runtime singularity initialized, version: 3.2.1-1.el7
, apiVersion: 3.2.1-1.el7

Then I ran a simple deployment of a singularity pod (a trimmed down version of your hello-kubernetes example). I launched this from the master node, not the app node where sycri is running.

[root@ip-172-16-241-23 ~]# oc create -f kube-hello.yml
deployment.apps/hello-kubernetes created
[root@ip-172-16-241-23 ~]# oc get pods
NAME                               READY     STATUS              RESTARTS   AGE
hello-kubernetes-8699564b7-v882c   0/1       ContainerCreating   0          4s

Sycri on the app node is getting information passed to it from kube!!!

# journalctl -xf -u sycri -l
...
a2bb354ba6/bundle/config.json
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.123255    1350 pod_runtime.go:49] Creating pod 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.123296    1350 client.go:133] Executing [singularity -q oci create --empty-process --sync-socket /var/run/singularity/pods/0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6/sync.sock -b /var/run/singularity/pods/0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6/bundle 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6]
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.195068    1350 sync.go:75] Received state 1 at /var/run/singularity/pods/0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6/sync.sock
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.232319    1350 sync.go:75] Received state 2 at /var/run/singularity/pods/0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6/sync.sock
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.234400    1350 pod_runtime.go:62] Starting pod 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.234451    1350 client.go:254] Executing [singularity -q oci start 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6]
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.263077    1350 sync.go:75] Received state 3 at /var/run/singularity/pods/0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6/sync.sock
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.308332    1350 pod.go:51] Bringing up network for pod 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: I0613 12:18:22.308391    1350 network.go:168] Network for pod 0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6 args: openshift-sdn:IgnoreUnknown=1;K8S_POD_NAMESPACE=default;K8S_POD_NAME=dockergc-8nh8r;K8S_POD_INFRA_CONTAINER_ID=0689cb0efa9fd457b9f9ddf55a6ee69d1bdd6326eaaf464d505bb8a2bb354ba6
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: E0613 12:18:22.313606    1350 main.go:47] /runtime.v1alpha2.RuntimeService/RunPodSandbox
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: Request: {"config":{"metadata":{"name":"dockergc-8nh8r","uid":"3363fc99-8d6a-11e9-8a61-0ecc46a145fa","namespace":"default"},"hostname":"dockergc-8nh8r","log_directory":"/var/log/pods/3363fc99-8d6a-11e9-8a61-0ecc46a145fa","dns_config":{"servers":["172.16.247.101"],"searches":["default.svc.cluster.local","svc.cluster.local","cluster.local","ec2.internal"],"options":["ndots:5"]},"labels":{"app":"dockergc","controller-revision-hash":"3112633316","io.kubernetes.pod.name":"dockergc-8nh8r","io.kubernetes.pod.namespace":"default","io.kubernetes.pod.uid":"3363fc99-8d6a-11e9-8a61-0ecc46a145fa","pod-template-generation":"1"},"annotations":{"kubernetes.io/config.seen":"2019-06-13T12:13:15.779324417-04:00","kubernetes.io/config.source":"api","openshift.io/scc":"privileged"},"linux":{"cgroup_parent":"/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod3363fc99_8d6a_11e9_8a61_0ecc46a145fa.slice","security_context":{"namespace_options":{"pid":1},"privileged":true,"seccomp_profile_path":"unconfined"}}}}
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: Response: null
Jun 13 12:18:22 ip-172-16-247-101.ec2.internal sycri[1350]: Error: rpc error: code = Internal desc = could not set up pod network interface: OpenShift SDN network process is not (yet?) available

So we've tied the 2 together!
Unfortunately the OpenShift SDN containers don't want to run with the Singularity runtime (at least that's my theory).