feat(k8s): map compose service ports to Kind extraPortMappings and support hostNetwork #993
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
K8s
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/stack-orchestrator#993
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/k8s-port-mappings-hostnetwork"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
_generate_kind_port_mappings now reads ports from compose services and
adds them to Kind's extraPortMappings with correct protocol handling
(TCP/UDP). Previously only ports 80/443 for Caddy were mapped, so
application ports like Solana gossip/RPC were unreachable from the host.
Also adds hostNetwork support: when any compose service declares
network_mode: host, the K8s pod spec gets hostNetwork: true and
dnsPolicy: ClusterFirstWithHostNet. This is required for workloads
like Solana validators that need direct host networking for UDP
gossip and TPU protocols.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
4d63448e7ctofbaa2eaa715197c57119tof305214ce1Checkout
From your project repository, check out a new branch and test the changes.