Repository navigation
chore: Change feature-server and operator base images to ubi9 - #4919
Merged
Merged
Conversation
Signed-off-by: Tommy Hughes <[email protected]>
lokeshrangineni
approved these changes
Jan 14, 2025
redhatHameed
approved these changes
Jan 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Move towards UBI base images for feast related containers. Also, removing
libarrow-devlibraries from feature-server image.Which issue(s) this PR fixes:
Fixes #4920
Misc
Removes unused
libarrow-devinstallation, which also reduces the size of the resulting image. This library hasn't been needed for close to 2 years since all Go feature server references were removed from the feast python code.#3554
For reference ... from the stale Feast docs on this removed component -
You must also install the Apache Arrow C++ libraries. This is because the Go feature server uses the cgo memory allocator from the Apache Arrow C++ library for interoperability between Go and Python, to prevent memory from being accidentally garbage collected when executing on-demand feature views.