https://flyte.org
Join Slack
How should I run the demo cluster if I want to have the flyte UI at a different port (other than 300...
# flyte-deployment
n
How should I run the demo cluster if I want to have the flyte UI at a different port (other than 30080) ?
b
endpoint: <http://localhost:30084|http://localhost:30084>
The endpoint here tells about your port. Cc @glamorous-carpet-83516
Hi @nice-judge-43061 , you can change the port in the endpoint, and this configuration can be changed in the config.yaml file.
t
@nice-judge-43061, are you able to spin up flyte on a different port?
n
@tall-lock-23197; No, I haven't been able do it. Though I modified the endpoint in the config file, I still get the console at the 30080 port only. http://localhost:30080/console/
b
After changing the port, did you restart the cluster?
n
Yes, I did
t
@glamorous-carpet-83516 / @icy-agent-73298, why is the config given in the demo start command not getting picked up 
flytectl demo start -c <your-config-file>
? I modified the port but it’s 30080 always.
n
Checked again now: Attaching the endpoint I specified and the output after restarting the demo cluster
b
I think the demo runs only on 30080 port or something on those lines.
https://github.com/flyteorg/flyte/issues/2503 - here is a discussion that mentions about demo using port 30080 only..
g
I think the demo cluster can run on different port if config changes. The message in command line always shows that 
UI is available at <https://localhost:30080>
because we hard code the message in flytectl. btw, demo container didn’t expose port 30083, so you can’t connect to it. https://github.com/flyteorg/flytectl/blob/0a68a579e91b72ee99b2f5c6bc15509f2d8bce7e/pkg/docker/docker_util.go#L117-L125
👀 1
i
Yes this require config file change in flyte repo called flyte.yaml and regeneration of the single binary Ref for this config .
Copy code
cmd/single/root.go:	RootCmd.PersistentFlags().StringVar(&cfgFile, "config", "", "config file (default is ./flyte.yaml)")
docker/sandbox-lite/flyte-entrypoint-dind.sh:flyte start --config /flyteorg/share/flyte.yaml &
docker/sandbox-lite/Dockerfile:COPY flyte.yaml /flyteorg/share/flyte.yaml
👀 1
flytectl config.yaml is just a client side config and mentions info on where to connect to the server.
👍 1
👀 1
steps that should work ideally. • Checkout flyte repo from github • Change the httpPort config in flyte.yaml -> lets say from 30080 -10080 • Change the port in Dockerfile to expose the port 10080 instead of old 30080 • docker build -t lit-image --file docker/sandbox-lite/Dockerfile • flytectl demo start --image lit-image
g
Another way to do that is updating this line to 
0.0.0.0:30083:30080
, and rebuild the flytectl by running 
make compile
. More detail about building the flytectl, check here
👍 2
167 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by