Skip to content

PodDisruptionBudget and TopologySpreadContraints for better HA configuration #5396

@jkleinlercher

Description

@jkleinlercher

Note: If you're requesting a Helm chart option that may be very niche and not useful to the community at large, please consider using Kustomize to apply "last mile" tweaks to the output of helm template to suit your needs instead.

Checklist

  • I've searched the issue queue to verify this is not a duplicate feature request.
  • I've pasted the output of kargo version, if applicable.
  • I've pasted logs, if applicable.

Proposed Feature

We configure Kargo for HA requirements (not fully distributed topology) and currently our HA specific settings are:

  api:
    replicas: 2
  externalWebhooksServer:
    replicas: 2
  webhooksServer:
    replicas: 2

However, for a stable HA configuration we think we would also need a PodDisruptionBudget and TopologySpreadContraints, so that the replicas are spread across different nodes (maybe also AZs) and the PDB takes care that at least on replica is running.

What do you think? Is this already planned? If not - and you think PDBs and TopologySpreadContraints are the things to achieve good HA - I could create a PR for it.

Motivation

Anyone who wants to set up Kargo in HA mode.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions