beacuse flyte-binary image has no version tag, it is replaced with fl… #5749
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking issue
Related to the discussion in Slack about the naming of the Flyte Docker image tag.
Why are the changes needed?
The current Docker image
flyte-binary
does not have a stable version tag, which leads to confusion during deployments. To prevent this, the image name is being changed toflyte-binary-release
, as agreed upon in the discussion.What changes were proposed in this pull request?
This PR proposes changing the Docker image name from
flyte-binary
toflyte-binary-release
in the Flyte Helm chart. This change ensures that a stable version tag is consistently used, reducing confusion and aligning with the team's agreed standards.Changes:
cr.flyte.org/flyteorg/flyte-binary-release
as the image repository.latest
and the pull policy toIfNotPresent
.How was this patch tested?
The changes were verified through updates to the Flyte Helm chart configuration. Further testing includes:
flyte-binary-release
image.Setup process
Screenshots
N/A
Check all the applicable boxes
Related PRs
None