Skip to content

[Design Proposal] Cross-VM Service communication with mTLS using Caddy - #1182

Draft
mayuka-c wants to merge 2 commits into
IBM:mainfrom
mayuka-c:caddy-mtls
Draft

[Design Proposal] Cross-VM Service communication with mTLS using Caddy#1182
mayuka-c wants to merge 2 commits into
IBM:mainfrom
mayuka-c:caddy-mtls

Conversation

@mayuka-c

Copy link
Copy Markdown
Member
  • Enabling cross service VM communication (between control plane and services on worker nodes) using Caddy as reverse_proxy.
  • Uses mTLS for secure communication.
  • Defines public, private ingress and egress blocks for proxy.

Copilot AI review requested due to automatic review settings July 27, 2026 11:06

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a design proposal describing how the AI-Services platform can enable cross-VM service communication using Caddy as ingress/egress reverse proxy with mTLS, including PKI bootstrapping and dynamic route registration via the Caddy Admin API.

Changes:

  • Documents VM roles, ports/listeners, and traffic flows for public HTTPS and private mTLS routing.
  • Specifies a CA/root + per-VM cert model and an onboarding/bootstrap flow for certificate provisioning.
  • Provides example Caddy JSON configurations and an Admin API route-registration approach.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


## 7. Caddy Configuration

All Caddy configuration is applied via the Admin API (`POST /config/` or `POST /load`). The examples below show the full JSON payload for each VM role.
@mayuka-c mayuka-c closed this Jul 27, 2026
@mayuka-c mayuka-c reopened this Jul 27, 2026
Signed-off-by: mayuka-c <Mayuka.C@ibm.com>
@mayuka-c mayuka-c changed the title [Design Proposal] Cross-VM Service communication with mTLS and Caddy [Design Proposal] Cross-VM Service communication with mTLS using Caddy Jul 28, 2026
@mayuka-c
mayuka-c marked this pull request as ready for review July 29, 2026 08:18
@mayuka-c

Copy link
Copy Markdown
Member Author

Moving this to draft as this will be work for 4Q26

@mayuka-c
mayuka-c marked this pull request as draft August 13, 2026 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants