Skip to content

in a K8s deployment, Sentinel Can't update the IP of the old master when the old master get back online again with different IP #8300

Description

@jhuang13

in a K8s deployment,
When the master redis pod goes down, the failover can happen normally. A slave will be selected as master by Sentinel.
When the old master (a new pod) get back online with a different pod IP but the same dns name. the Sentinel will not refresh the IP based on the old master's dns name. so the old master will be isolated as the master has no info about the Sentinel cluster.
Is there a way to make the Sentinel work on K8s

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