Hi all! When deploying the whole stack using the <...
# all-things-deploymentl
limited-cricket-18852
11/11/2021, 12:41 PMHi all! When deploying the whole stack using the Helm chart, aren’t we supposed to deploy the MCE and MAE jobs? I can’t find them running, am I missing something?
limited-cricket-18852
11/11/2021, 12:41 PMHere is everything I have (running a local kubernetes in Docker Desktop):
Copy code
➜ ~ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/datahub-datahub-frontend-9d5b89c87-jzxz6 1/1 Running 3 42h
pod/datahub-datahub-gms-544fdbb865-wg29h 1/1 Running 0 42h
pod/datahub-datahub-upgrade-job-kmpsr 0/1 Completed 0 21h
pod/datahub-elasticsearch-setup-job-pt7cp 0/1 Completed 0 21h
pod/datahub-kafka-setup-job-gqzkf 0/1 Completed 0 21h
pod/datahub-mysql-setup-job-nzglm 0/1 Completed 0 21h
pod/elasticsearch-master-0 1/1 Running 0 42h
pod/elasticsearch-master-1 1/1 Running 0 42h
pod/prerequisites-cp-kafka-0 2/2 Running 0 42h
pod/prerequisites-cp-kafka-1 2/2 Running 1 42h
pod/prerequisites-cp-kafka-2 2/2 Running 1 42h
pod/prerequisites-cp-schema-registry-6b464bfbc5-npn7v 2/2 Running 0 42h
pod/prerequisites-cp-zookeeper-0 2/2 Running 0 42h
pod/prerequisites-mysql-0 1/1 Running 9 42h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/datahub-datahub-frontend ClusterIP 10.108.108.60 <none> 9002/TCP 42h
service/datahub-datahub-gms ClusterIP 10.97.99.71 <none> 8080/TCP 42h
service/elasticsearch-master ClusterIP 10.110.212.168 <none> 9200/TCP,9300/TCP 42h
service/elasticsearch-master-headless ClusterIP None <none> 9200/TCP,9300/TCP 42h
service/kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 43d
service/prerequisites-cp-kafka ClusterIP 10.102.85.51 <none> 9092/TCP,5556/TCP 42h
service/prerequisites-cp-kafka-headless ClusterIP None <none> 9092/TCP 42h
service/prerequisites-cp-schema-registry ClusterIP 10.109.65.91 <none> 8081/TCP,5556/TCP 42h
service/prerequisites-cp-zookeeper ClusterIP 10.106.49.63 <none> 2181/TCP,5556/TCP 42h
service/prerequisites-cp-zookeeper-headless ClusterIP None <none> 2888/TCP,3888/TCP 42h
service/prerequisites-mysql ClusterIP 10.96.124.136 <none> 3306/TCP 42h
service/prerequisites-mysql-headless ClusterIP None <none> 3306/TCP 42h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/datahub-datahub-frontend 1/1 1 1 42h
deployment.apps/datahub-datahub-gms 1/1 1 1 42h
deployment.apps/prerequisites-cp-schema-registry 1/1 1 1 42h
NAME DESIRED CURRENT READY AGE
replicaset.apps/datahub-datahub-frontend-9d5b89c87 1 1 1 42h
replicaset.apps/datahub-datahub-gms-544fdbb865 1 1 1 42h
replicaset.apps/prerequisites-cp-schema-registry-6b464bfbc5 1 1 1 42h
NAME READY AGE
statefulset.apps/elasticsearch-master 2/2 42h
statefulset.apps/prerequisites-cp-kafka 3/3 42h
statefulset.apps/prerequisites-cp-zookeeper 1/1 42h
statefulset.apps/prerequisites-mysql 1/1 42h
NAME SCHEDULE SUSPEND ACTIVE LAST SCHEDULE AGE
cronjob.batch/datahub-datahub-cleanup-job-template * * * * * True 0 <none> 42h
cronjob.batch/datahub-datahub-restore-indices-job-template * * * * * True 0 <none> 42h
NAME COMPLETIONS DURATION AGE
job.batch/datahub-datahub-upgrade-job 1/1 80s 21h
job.batch/datahub-elasticsearch-setup-job 1/1 19s 21h
job.batch/datahub-kafka-setup-job 1/1 108s 21h
job.batch/datahub-mysql-setup-job 1/1 10s 21hr
rapid-sundown-8805
11/11/2021, 1:47 PMThey're embedded in GMS, theres a variable to have them separate
teamwork 1
l
limited-cricket-18852
11/11/2021, 1:53 PMohh alright, thanks !
b
big-carpet-38439
11/11/2021, 5:25 PMYes that's correct! You can also deploy them as standalone, but that's only recommended in cases where you'd want to scale them separately
l
limited-cricket-18852
11/11/2021, 6:10 PMgo it. Thanks !
2 Views