Skip to content

Secure CSI Driver TCP Connections via Substrate Pod Identity - #956

Draft
hajiler wants to merge 1 commit into
agent-substrate:mainfrom
hajiler:managed-tcp
Draft

Secure CSI Driver TCP Connections via Substrate Pod Identity#956
hajiler wants to merge 1 commit into
agent-substrate:mainfrom
hajiler:managed-tcp

Conversation

@hajiler

@hajiler hajiler commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

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

It's a good idea to open an issue first for discussion.

  • [X ] Tests pass
  • Appropriate changes to documentation are included in the PR

@hajiler
hajiler force-pushed the managed-tcp branch 6 times, most recently from 7837061 to ac4da29 Compare August 14, 2026 22:28
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.

1 participant