Deepstream.io on Kubernetes cluster

0 votes

Is it possible to deploy DeepStream and Redis on multi-node cluster using Kubernetes?

This is the docker compose file for DeepStream, Redis, RethinkDB

version: '2'
services:
deepstream:
    build: "."
    ports:        - 6020:6020"
        - "6021:6021"
    volumes:
        - ./conf:/usr/local/deepstream/conf
        - ./var:/usr/local/deepstream/var
    depends_on:
        - redis
        - rethinkdb
deepstream-search-provider:
    # build: "../deepstream.io-provider-search-rethinkdb/1.1.1"
    image: deepstreamio/deepstream.io-provider-search-rethinkdb
    environment:
        - DEEPSTREAM_HOST=deepstream
        - DEEPSTREAM_PORT=6021
        - RETHINKDB_HOST=rethinkdb
    depends_on:
        - depstream
redis:
    image: redis:alpine
    ports:
        - "6379:6379"
rethinkdb:
    image: rethinkdb
    ports:
        - "28015:28015"
        - "8080:8080"
    volumes:
        - ./rethinkdb_data:/data/rethinkdb_data

When I tried converting docker-compose.yaml to kebernetes yaml using compose I’m getting the following warnings

WARN Unsupported depends_on key - ignoring
WARN Volume mount on the host "./conf" isn't supported - ignoring path on the host
WARN Volume mount on the host "./var" isn't supported - ignoring path on the host
WARN Volume mount on the host "./rethinkdb-data" isn't supported - ignoring path on the host
INFO Kubernetes file "deepstream-service.yaml" created
INFO Kubernetes file "deepstream-search-provider-service.yaml" created
INFO Kubernetes file "redis-service.yaml" created
INFO Kubernetes file "rethinkdb-service.yaml" created
INFO Kubernetes file "deepstream-deployment.yaml" created
INFO Kubernetes file "deepstream-claim0-persistentvolumeclaim.yaml" created
INFO Kubernetes file "deepstream-claim1-persistentvolumeclaim.yaml" created
INFO Kubernetes file "deepstream-search-provider-deployment.yaml" created
INFO Kubernetes file "redis-deployment.yaml" created
INFO Kubernetes file "rethinkdb-deployment.yaml" created
INFO Kubernetes file "rethinkdb-claim0-persistentvolumeclaim.yaml" created
Sep 3, 2018 in Kubernetes by Hannah
• 14,070 points
130 views

1 answer to this question.

0 votes

Kompose doesn’t support host volume mounting. Instead you can create volume manually and then insert the respective data.

answered Sep 3, 2018 by Kalgi
• 40,460 points
Hello

Thank you for your reply . I face the same issue. Can you explain please, how to insert the respective data in docker compose yml?

Related Questions In Kubernetes

0 votes
1 answer

automating cluster setup and app deplument on kubernetes

Go through Google Cloud Deployment Manager. it automates ...READ MORE

answered Jul 5, 2018 in Kubernetes by ajs3033
• 7,280 points
42 views
0 votes
1 answer

oci runtime error while running kubernetes on rancher cluster

You need to switch Docker to 1.12.x; ...READ MORE

answered Sep 6, 2018 in Kubernetes by Kalgi
• 40,460 points
93 views
0 votes
1 answer

Accessing remote kubernetes cluster on azure using kubectl

So, try this. Edit your kube config ...READ MORE

answered Sep 11, 2018 in Kubernetes by ajs3033
• 7,280 points
58 views
0 votes
1 answer

Set up kubernetes cluster on ubuntu

Do kubeadm reset and start all over ...READ MORE

answered Oct 5, 2018 in Kubernetes by Kalgi
• 40,460 points
50 views
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
2,166 views
+3 votes
1 answer
0 votes
1 answer

“403 Insufficient Permission” while creating a Kubernetes Cluster on Google Cloud instance

To run ./cluster/kube-up.sh, you most likely need compute scope ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 40,460 points
128 views
0 votes
1 answer

Unable to run Kubernetes on rancher cluster

switch Docker to 1.12.x; Kubernetes doesn't support ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 40,460 points
134 views