fix: Mount TLS volumes for init container for TLS-enabled registries#6199
Merged
ntkathole merged 1 commit intofeast-dev:masterfrom Mar 31, 2026
Merged
fix: Mount TLS volumes for init container for TLS-enabled registries#6199ntkathole merged 1 commit intofeast-dev:masterfrom
ntkathole merged 1 commit intofeast-dev:masterfrom
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
franciscojavierarceo
approved these changes
Mar 31, 2026
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
2 participants
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:
When a FeatureStore CR uses TLS-enabled services (local TLS, remote registry TLS, or custom CA bundles), the feast-apply init container fail to connect to TLS-secured endpoints because they lack the necessary TLS certificate volume mounts. init containers need the same PVC mounts that main containers already get.
Additionally, removed the feastProject name matching constraint in getRemoteRegistryFeastHandler that required the referencing and referenced FeatureStore CRs to use the same feastProject name. This was overly restrictive - the operator should allow different project configurations to reference a shared remote registry without enforcing name equality.
changes
Which issue(s) this PR fixes:
Fixes #6197