Skip to content

ate-setup does not allow customizing the resource configurations of Substrate components #2579

Description

@haiyanmeng

Currently, ate-setup does not allow users to customize the resource configurations of Substrate components (such as replicas and cpu/mem). The default setting does not work for Substrate clusters having higher performance and scalability needs.

cc Steven Shriver (@stshrive) Max Smythe (@maxsmythe)

Activity

  1. added this to the M3 milestone on Oct 13, 2026
  2. added
    kind/featureAn enhancement / feature request or implementation
    prio/P0Highest priority / required for next milestone
    on Oct 13, 2026
  3. zlammerts-svg commented on Oct 14, 2026

    @zlammerts-svg
    Collaborator

    I will remove the M3 tag for now. Steven Shriver (@stshrive) please share your design doc with Tim Hockin (@thockin) for review.

  4. removed this from the M3 milestone on Oct 14, 2026
  5. stshrive commented on Oct 15, 2026

    @stshrive
    Collaborator

    The way I see this is that the configuration knobs needed for this also align with the overall installer design options I have documented in the extensible install proposal Specifically, Options 3 and/or 4 in the doc. I don't know that rushing more features into the installer right now is the right call without more design consideration.

  6. stshrive commented on Oct 15, 2026

    @stshrive
    Collaborator

    Minimally, there is the option of exposing just an overlay for replicas, CPU, Mem, etc. and removing the defaults from the base CRDs.

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

Metadata

Metadata

Labels

area/dev-infrakind/featureAn enhancement / feature request or implementationprio/P0Highest priority / required for next milestone

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions