fix: Fixed tls issue when running both grpc and rest servers #5617
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 both gRPC and REST registry servers are enabled with TLS, the Feast operator was generating separate TLS certificates for each service, causing hostname validation failures. The gRPC client would receive a "Peer name not in peer certificate" error because it was trying to connect to the gRPC service hostname but the certificate only contained the REST service hostname.
Error:
This PR implemented a unified TLS certificate approach using Subject Alternative Names (SANs). When both gRPC and REST are enabled, use the gRPC service name as the primary certificate and add the REST service hostname as a Subject Alternative Name in the certificate.