Skip to content

Determine template resolution in Flyte UI#1

Open
jld-adriano wants to merge 1 commit intomasterfrom
cursor/determine-template-resolution-in-flyte-ui-a248
Open

Determine template resolution in Flyte UI#1
jld-adriano wants to merge 1 commit intomasterfrom
cursor/determine-template-resolution-in-flyte-ui-a248

Conversation

@jld-adriano
Copy link
Copy Markdown

## Tracking issue
<!--
If your PR fixes an open issue, use `Closes #999` to link your PR with the issue.
Example: Closes #999

If your PR is related to an issue or PR, use `Related to #999` to link your PR.
Example: Related to #999

Remove this section if not applicable
-->

## Why are the changes needed?

This PR provides clear documentation on how Flyte resolves console URL templates, starting from Helm chart configurations, through FlyteAdmin, and finally to runtime URL construction for UI links. This addresses a common question about Flyte's internal workings for UI link generation.

## What changes were proposed in this pull request?

This PR introduces a new markdown document, `flyte-console-url-resolution.md`, which comprehensively explains the end-to-end process of how Flyte resolves console URLs. The document details:
*   Helm chart configuration (`values.yaml`, `configmap.yaml`)
*   Configuration loading in FlyteAdmin (`application_configuration.go`)
*   Embedding of the console URL into the workflow CRD (`k8s_executor.go`, `workflow.go`)
*   Runtime construction of task-specific URLs (`k8s_resource_adds.go`)
*   The final URL template format.
It also lists key files and their roles in this resolution pipeline.

## How was this patch tested?

This is a documentation-only change. The content was generated through a detailed analysis of the Flyte codebase to accurately describe the console URL resolution process. No code changes were made, and therefore no new tests were added or existing tests run.

### Labels

- **added**

### Setup process

### Screenshots

## Check all the applicable boxes <!-- Follow the above conventions to check the box -->

- [x] I updated the documentation accordingly.
- [ ] All new and existing tests passed.
- [ ] All commits are signed-off.

## Related PRs

<!-- Add related pull requests for reviewers to check -->

## Docs link

<!-- Add documentation link built by CI jobs here, and specify the changed place -->

Slack Thread

Co-authored-by: adriano <adriano@exa.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants