Tommy Li

Update: I rewritten the instructions and travis CI to use the helm charts only for deployment. Since the GitHub page won't be available until we merge it to master, anyone...

Hi @stock99, it looks like the script didn't find the right pod name from your Kubernetes cluster. Can you echo your pod name with the below commands? Thanks. ```shell ui_pod=$(kubectl...

Hi @stock99, I updated the script at #150 to make it able to run with K8S 1.8.x. Let me know if you encounter any new issue.

Hi @Earl-chen, it looks like the volume configmap is not being created. Can you run the following script to generate the necessary configmap? Thanks. ```shell pushd bin ./create_static_volumes.sh ./create_static_volumes_config.sh popd...

Thank you for taking the time to redeploy FfDL. It looks like many of the pods failed liveness probe. Which means those microservices might not able to communicate with each...

@Eric-Zhang1990 `./create_static_volumes.sh` and `./create_static_volumes_config.sh` should able to create the static-volumes and v2 configmap for you. Do you still encounter problems with `configmap "static-volumes" not found`?

@Eric-Zhang1990 It looks like you deployed the static-volumes at the `default` namespace while FfDL is at `kube-system` namespace. You could deploy FfDL using helm with the namespace flag (e.g. `helm...

The `SHARED_VOLUME_STORAGE_CLASS` should be your default storageclass in your Kubernetes cluster. You can check the storageclass with `kubectl get storageclass`

Thank you for taking time to debug this. Elasticsearch should be part of the `storage-0` container. It could be the Elasticsearch service didn't properly enabled. Can you run `kubectl get...

Hi @Eric-Zhang1990, Sorry for the late reply. Regrading the elastic search error, you supposed to have the following logs at the end of the `storage-0` container. ``` [2019-01-24T01:17:28,500][WARN ][o.e.b.BootstrapChecks ]...