Channels
#flyte-deployment
Title
h
Hampus Rosvall
03/30/2022, 6:55 AMI deployed Flyte on EKS without an Ingress due to running an older version of ALB Controller than the required one. It works fine to port-forward to the
FlyteAdminFlyteConsoley
Yuvraj
03/30/2022, 7:43 AMAfter port forwarding your console is working but it is trying flyteadmin connection through Ingress that’s why you are seeing that error
h
Hampus Rosvall
03/30/2022, 8:01 AMRight, so basically an update to ALB Controller is needed then. Thanks
👍 1
k
Ketan (kumare3)
03/30/2022, 1:31 PM
There is a way to tell console to use a different host:port instead
It's called admin_api_url https://docs.flyte.org/en/latest/concepts/console.html#running-flyteconsole
You can update it in console config
h
Hampus Rosvall
03/31/2022, 8:46 AMOk thanks for the clarification @Ketan (kumare3). So basically I extend the
values-eks.yamlADMIN_API_URLvalues.yamlAnd I guess the key
ADMIN_API_URLk
Ketan (kumare3)
03/31/2022, 12:49 PM
That is right. Cc @Yuvraj I think the disable auth should be removed. Also cc @Jason Porter can we make the baseurl /console as the default
👍 1
j
Jason Porter
03/31/2022, 5:19 PMYeah we removed
DISABLE_AUTHv0.34.0h
Hampus Rosvall
04/01/2022, 6:28 AMGot it, will try that out. Thanks 🙂
Follow up, I used the following in my
values.yamlFlyteConsole Copy code
configmap:
console:
ADMIN_API_URL: <adress>.<http://eu-west-1.elb.amazonaws.com|eu-west-1.elb.amazonaws.com>k
Ketan (kumare3)
04/01/2022, 2:02 PM
Is this url right - can you try api/v1/projects on that endpoint
h
Hampus Rosvall
04/01/2022, 2:17 PMSure
Seems to work from a Pod running in the same cluster
Copy code
root@ubuntu-client:/# curl -v http://<host>/api/v1/projects
...
{"projects":[{"id":"determined","name":"determined","domains":[{"id":"development","name":"development"},{"id":"staging","name":"staging"},{"id":"production","name":"production"}],"labels":{}},{"id":"flyteexamples","name":"flyteexamples","domains":[{"id":"development","name":"development"},{"id":"staging","name":"staging"},{"id":"production","name":"production"}],"description":"flyteexamples description"},{"id":"flytesnacks","name":"flytesnacks","domains":[{"id":"development","name":"development"},{"id":"staging","name":"staging"},{"id":"production","name":"production"}],"description":"flytesnacks description"},{"id":"flytetester","name":"flytetester","domains":[{"id":"development","name":"development"},{"id":"staging","name":"staging"},{"id":"production","name":"production"}],"description":"flytetester description"},{"id":"mnist","name":"mnist","domains":[{"id":"development","name":"development"},{"id":"staging","name":"staging"},{"id":"production","name":"production"}],"labels":{}}]}root@ubuntu-client:/#And I am getting this error if it is of any help:
Command:
Copy code
k port-forward svc/flyteconsole 1234:80k
Ketan (kumare3)
04/01/2022, 3:02 PM
Cc @Jason Porter l, @Hampus Rosvall I can help probably around 9:00 am pst
h
Hampus Rosvall
04/01/2022, 3:38 PMThat's very kind! I am off since I work in Sweden, we can take it on Monday if that works for you :)
k
Ketan (kumare3)
04/01/2022, 3:40 PM
We can try
h
Hampus Rosvall
04/03/2022, 5:09 PMWhen I check the logs from the console Pod I get the following after port-forwarding to `svc/flyteconsole`:
Copy code
::ffff:127.0.0.1 - - [03/Apr/2022:17:05:15 +0000] "GET /<host>/api/v1/projects HTTP/1.1" 304 - "<http://localhost:1234/console>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Firefox/98.0"k
Ketan (kumare3)
04/03/2022, 5:59 PM
304, weird?
h
Hampus Rosvall
04/03/2022, 6:00 PMYeah, I also thought about that
But I guess 304 makes sense since I possibly have not modified anything on the projects resource
k
Ketan (kumare3)
04/03/2022, 6:02 PM
@Hampus Rosvall hmm, i do not think we publish any cache headers
h
Hampus Rosvall
04/03/2022, 6:09 PM@Ketan (kumare3) I realize now that I am missing the protocol and port part of the
ADMIN_API_URLk
Ketan (kumare3)
04/03/2022, 6:09 PM
ohh ya
oops
lets try that
h
Hampus Rosvall
04/03/2022, 6:11 PMHope it’s as simple as that. Guess that I should use port 80 right?
k
Ketan (kumare3)
04/03/2022, 6:12 PM
hmm, it should be the localhost port-forward port
so lets say, admin is port-forwarded to - “localhost:8080” - then you should be able to say “localhost:8080/api/v1/projects” in your browser
if that works then,
In console
ADMIN_API_URL=<http://localhost:8080>h
Hampus Rosvall
04/03/2022, 6:16 PMHm, should I really reference localhost in the ConfigMap? I though I should reference the LoadBalancer address
k
Ketan (kumare3)
04/03/2022, 6:16 PM
yes
ohh hold on, so your LB is working?
have you tried
<http://lb>:port/api/v1/projectsif that works, then absolutely, just reference the
lb:porth
Hampus Rosvall
04/03/2022, 6:18 PMYes it works!
k
Ketan (kumare3)
04/03/2022, 6:18 PM
ok, then lets use the lb
but then you can simply use the
lb:porth
Hampus Rosvall
04/03/2022, 6:20 PMRight, but I still need to fix the
ADMIN_API_URLlb:port is working fine using CURL, but I get network error in the console when I use
ADMIN_API_URL=<http://lb>:portk
Ketan (kumare3)
04/03/2022, 6:22 PM
hmm
is it https?
BTW, I think you will really like this - https://github.com/flyteorg/flyte/pull/2265
h
Hampus Rosvall
04/03/2022, 6:24 PMWow that looks really cool. Will it run on Kubernetes aswell?
k
Ketan (kumare3)
04/03/2022, 6:29 PM
it can run anywhere
you can even run it on an ec2 instance
and then just point to an eks cluster
thats it
eventhough the intention is to speed up sandbox, it is production grade
❤️ 1
and you can simply increase the replicas of this single binary (not too many), to get a smallish cluster running in not time
h
Hampus Rosvall
04/03/2022, 6:31 PMLooks extremely cool!
k
Ketan (kumare3)
04/03/2022, 6:31 PM
ya slated to be out in one week
it also packages console with itself
cc @Jason Porter when you do get a chance, just simply replacing admin_api_url with admin’s remote address work right?
5 Views