<p>I deployed a Redis standalone in Openshift (CRC) using bitnami helm chart (<a href="https://github.com/bitnami/charts/tree/main/bitnami/redis" rel="nofollow noreferrer">https://github.com/bitnami/charts/tree/main/bitnami/redis</a>)</p>
<p>I used these parameters:</p>
<pre><code>helm repo add my-repo https://charts.bitnami.com/bitnami

helm upgrade --install redis-ms my-repo/redis \
--set master.podSecurityContext.enabled=false \
--set master.containerSecurityContext.enabled=false \
--set auth.enabled=false \
--set image.debug=true \
--set architecture=standalone
</code></pre>
<p>I can see a Redis Master node pod &quot;Ready to accept connections&quot;
Then I create a Route to expose redis outside the cluster:</p>
<pre><code>kind: Route
apiVersion: route.openshift.io/v1
metadata:
  name: redis  
spec:
  host: redis-ms.apps-crc.testing
  to:
    kind: Service
    name: redis-ms-master
  port:
    targetPort: tcp-redis
  wildcardPolicy: None
</code></pre>
<p>But when I try to connect to &quot;redis-ms.apps-crc.testing:80&quot; I got:</p>
<pre><code>&quot;Unknown reply: H&quot;
</code></pre>
<p>While if I use <code>oc port-forward --namespace redis-ms svc/redis-ms-master 6379:6379</code> and then I connect to &quot;localhost:6379&quot; it works</p>

Fabry
<p>OpenShift <code>Route</code>s are limited to HTTP(S) traffic, due to how the <a href="https://docs.openshift.com/container-platform/4.11/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.html" rel="nofollow noreferrer">router sends traffic with SNI</a>.</p>
<blockquote>
<p>An Ingress Controller is configured to accept external requests and proxy them based on the configured routes. This is limited to HTTP, HTTPS using SNI, and TLS using SNI, which is sufficient for web applications and services that work over TLS with SNI.</p>
</blockquote>
<p>If you need to expose non-HTTP traffic, like a database or Redis instance in your case, you can <a href="https://docs.openshift.com/container-platform/4.11/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.html#nw-create-load-balancer-service_configuring-ingress-cluster-traffic-load-balancer" rel="nofollow noreferrer">expose this <code>Service</code> directly as a <code>LoadBalancer</code> type <code>Service</code></a>. This would look something like below for your Redis <code>Service</code></p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: v1
kind: Service
metadata:
  name: redis-ms-master
spec:
  ports:
  - name: tcp-redis
    port: 6379 
    targetPort: redis
  type: LoadBalancer 
  selector:
    name: app.kubernetes.io/component: master 

</code></pre>
<p>Additionally, it actually looks like that specific helm chart supports <a href="https://github.com/bitnami/charts/tree/main/bitnami/redis#redis-master-configuration-parameters" rel="nofollow noreferrer">setting this as a configuration option</a>, <code>master.service.type</code>.</p>
