Skip to content

RabbitMQ service: client access over TLS (S-023-19) #507

Closed

Description

@shipmill-romamo

Builds part of spec S-023, docs/specs/023-rabbitmq-service.md: the acceptance criteria below. Each needs a test that names its id (test_s023_<k>_..., or a proves: S-023-19 comment line).

Scope: clientAccess: the TLS listener on each node's declared IPv4, the certificate requirement, and the nftables rules scoped to allowedSources.

  • S-023-19: With clientAccess of allowedSources: [10.0.0.0/24], jobs connects to each node from an allowed address on 5671 verifying the project CA, a plain connection to 5672 from that address is refused, and each ruleset holds ip saddr 10.0.0.0/24 tcp dport 5671 accept and no unrestricted rule for a RabbitMQ port

Depends on #506

Activity

  1. shipmill-romamo commented on Nov 17, 2026

    @shipmill-romamo
    ContributorAuthor

    Triage: implement. Serves: G-1, G-3.

    Builds S-023-19 of spec 023 (docs/specs/023-rabbitmq-service.md, approved in #500), for #502: client access over TLS, as the body above scopes it.

    It starts once #506 (one node converged) closes; its Depends on line holds it until then. I'll link the PR here.

  2. shipmill-romamo commented on Nov 18, 2026

    @shipmill-romamo
    ContributorAuthor

    PR: #542. With clientAccess, each node listens with TLS on <IPv4>:5671 with its certificate from the project CA (the issuing path MariaDB uses), plain 5672 stays on 127.0.0.1, and the ruleset holds ip saddr 10.0.0.0/24 tcp dport 5671 accept and no unrestricted RabbitMQ rule; without clientAccess the render is unchanged.

    Proven by tests: the rules, the listener settings, and the certificate and key handling of S-023-19. Not verified on a real host: jobs logging in on 5671 while checking the project CA, and a plain 5672 connection from an allowed address being refused.

    #541 (the cluster, #508) touches the same listener template and refusal task: whichever lands second is rebased to cover three nodes with clientAccess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions