Skip to content

feat(kube): restrict MC RCON access to kilobase namespace#7589

Merged
h0lybyte merged 1 commit intodevfrom
trunk/mc-rcon-internal-1772583917
Mar 4, 2026
Merged

feat(kube): restrict MC RCON access to kilobase namespace#7589
h0lybyte merged 1 commit intodevfrom
trunk/mc-rcon-internal-1772583917

Conversation

@h0lybyte
Copy link
Member

@h0lybyte h0lybyte commented Mar 4, 2026

Summary

  • Adds a NetworkPolicy to the MC Kubernetes manifests that restricts RCON (port 25575) access to only the kilobase and mc namespaces
  • Game (25565/TCP), Bedrock (19132/UDP), and Resource Pack (8080/TCP) ports remain unrestricted
  • RCON is accessible internally at mc-service.mc.svc.cluster.local:25575

Test plan

  • Verify RCON connection succeeds from a pod in the kilobase namespace
  • Verify RCON connection is denied from pods in other namespaces
  • Verify game/bedrock/resource-pack traffic is unaffected

RCON (port 25575) is now only accessible from the kilobase and mc
namespaces. Game, bedrock, and resource-pack ports remain open.
@github-actions
Copy link
Contributor

github-actions bot commented Mar 4, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@h0lybyte h0lybyte merged commit cb0b602 into dev Mar 4, 2026
5 checks passed
@h0lybyte h0lybyte deleted the trunk/mc-rcon-internal-1772583917 branch March 4, 2026 01:29
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