Skip to content

Potentially add simpler ways of specifying anti-affinity #149

Description

@cheahjs

#136 introduces the ability to specify the affinity field for the underlying etcd pods.

However, writing affinity rules requires an understanding of how the operator internally adds labels to pods. Given that for high availability the pods should be spread across multiple failure domains (nodes/availability zones), we might want to consider adding a simple API for specifying some topologyKey to spread pods across.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions