Secure CSI Driver TCP Connections via Substrate Pod Identity - #956
Draft
hajiler wants to merge 1 commit into
Draft
Secure CSI Driver TCP Connections via Substrate Pod Identity#956hajiler wants to merge 1 commit into
hajiler wants to merge 1 commit into
Conversation
hajiler
force-pushed
the
managed-tcp
branch
6 times, most recently
from
August 14, 2026 22:28
7837061 to
ac4da29
Compare
CONV=08b81b20-9977-45df-b98e-9e340bc55e2d
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.
Secures network-based gRPC connections between the ate-api control plane and CSI driver controller services using mutual TLS (mTLS) backed by Substrate's Pod Identity.
Requests from ate-api to CSI driver controllers occur over the network, as configured via the CSIDriverConfig custom resource. This PR extends the CSIDriverConfig CRD to include a tls configuration section, which leverages
Substrate's Pod Identity certificate infrastructure (managed by podcertcontroller) to secure these
TCP connections using mTLS. Because standard CSI drivers typically communicate over Unix domain sockets, a proxy sidecar (e.g., envoy) is added to the CSI controller deployment to terminate TLS and forward requests to the local CSI socket.
#232