Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: abandoning the optimization of the old bento #179

Closed

Conversation

yetone
Copy link
Member

@yetone yetone commented Jan 22, 2025

No description provided.

@@ -1082,7 +1082,7 @@ func getBentoImageName(bentoRequest *resourcesv1alpha1.BentoRequest, dockerRegis
}

func isImageStoredInS3(bentoRequest *resourcesv1alpha1.BentoRequest) (storedInS3 bool) {
return bentoRequest.Annotations[commonconsts.KubeAnnotationImageStoredInS3] == commonconsts.KubeLabelValueTrue
return bentoRequest.Annotations[commonconsts.KubeAnnotationImageStoredInS3] == commonconsts.KubeLabelValueTrue && bentoRequest.Annotations["yatai.ai/bento-image-spec"] == "2"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

‌‌‌I have a small immature suggestion: can we control whether to use bento-image-builder only through KubeAnnotationImageStoredInS3 on the bentocloud side, and set it to True by default? When encountering issues, remind users to set it to false in the UI.

@xianml xianml self-requested a review January 23, 2025 06:13
@yetone yetone closed this Feb 6, 2025
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