Skip to content

[Feature]: Introduce elasticstack_manage_ca (collection-managed CA vs bring-your-own) #532

Open

Description

@afeefghannam89

One job hidden inside elasticstack_full_stack: whether the collection acts as its own Certificate Authority — generating the CA with elasticsearch-certutil and distributing ca.crt + node/component certificates across the roles.

Add elasticstack_manage_ca (default true) to control exactly this. When false, the collection generates/distributes nothing and the user brings their own CA/certificates via the existing *_tls_* variables (externally-managed or cloud stack). Decouples "collection owns the PKI" from "collection deploys the components".

Breaking → 2.0.0. Part of #531.

Activity

  1. added this to the 2.0.0 milestone on Aug 7, 2026
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

    component:elasticstackroles/elasticstack - meta role, shared variables

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions