https://flyte.org logo
#contribute
Title
# contribute
f

Fabio Grätz

02/05/2024, 12:45 PM
I saw that work has been done recently by Eduardo about dynamic log links, the first use case being Flyin. Is there a plan for exposing the vscode service to the outside world in OSS? I assume we wouldn’t want to adapt the ingress … Am I correct that flyin so far is only a flytekit plugin with no logic in flyteplugins/propeller? How will the k8s service be created for vscode tasks?
d

David Espejo (he/him)

02/05/2024, 2:11 PM
Cc @Eduardo Apolinario (eapolinario) @Byron Hsu Also, tomorrow's community meeting will feature this plugin
f

Fabio Grätz

02/05/2024, 2:13 PM
nice 👏
I’ll try to join
k

Ketan (kumare3)

02/05/2024, 2:52 PM
Yes Fabio, the link will be automatically added to the log links. Users can setup their own ingress rules. I am just hoping it does not become another support burden
f

Fabio Grätz

02/05/2024, 2:56 PM
Yeah Ingress can be tricky to debug for many 😕
But if propeller will adapt the ingress according to rules, I assume that propeller will also create a service for the task pod right? In contrast to port-forwarding, you can’t target a pod without a service in an ingress or am I missing something?
k

Ketan (kumare3)

02/05/2024, 3:03 PM
I do not think we will do that
I think the way I am thinking is to send back a pre configured link
f

Fabio Grätz

02/05/2024, 3:04 PM
But how will the vscode be exposed through the ingerss without a service object?
k

Ketan (kumare3)

02/05/2024, 3:04 PM
You can connect to pods directly
f

Fabio Grätz

02/05/2024, 3:04 PM
Interesting, haven’t seen this but then it makes sense 👍
k

Ketan (kumare3)

02/05/2024, 3:05 PM
Needs special ingress stuff - but I think complicating propeller to create and manage service lifecycle is for now out of scope
f

Fabio Grätz

02/05/2024, 3:05 PM
With “it” I mean expose pod through ingress without service
2 Views