cristobalcl commented on issue #2919: Launch PEX on Kubernetes fails URL: https://github.com/apache/incubator-heron/issues/2919#issuecomment-398713766 The lapse in the timestamps of the logs is because I was using computers in different time zones (deploying from my local computer into the cluster). I was watching the logs in real-time and I can say those logs are related to the issue. Anyway, it's possible that I was missing another important logs of other system that is needed to debug, if so I could replicate the problem. In the other hand, I'm looking for an alternative way of deploying the PEX. I was trying to use the [S3 uploader](https://apache.github.io/incubator-heron/docs/operators/deployment/uploaders/s3/), but I can not understand how it works. I could open another issue for this, if you wish, but anyway... Firstly, I have no idea how to configure the CLI. I have tried multiple combinations of parameters and configuration files, but the only thing I have get to work is modifying the `uploader.yaml` for the `local` config and running `heron submit local …`. And doing so the PEX is uploaded to S3 succesfully... But nothing more. Ok, the PEX is in the S3 bucket, now what? How does Heron download the PEX and submit this and run the topology? Sorry if this is obvious, but I have seen no example anywhere about using the S3 uploader. And again, I don't understand how to use the Heron CLI with the `cluster/[role]/[env]`, configurations files, `--config-path` and `--config-property` arguments,... What I usually do with Kubernetes is: ```bash heron config heron set service_url http://…/heron-apiserver:9000 heron submit heron "dist/xxxxxxxxxxx.pex" --verbose - […] ``` And this worked like a charm. But I have no idea which `uploader.yaml` I need to edit, or how to set up this to use the S3 uploader. And, again, I don't know how the server will launch the topology, or if I need to config anything in the Helm chart of Heron. Thank you very much!
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
