Skip to content

Chore: Claudie with non-static IPs on instances #1969

@Despire

Description

@Despire

Description

Reconciliation loop does not handle well VMs that are created with IPs that change during the lifetime of the
instance. For example a VM is restarted and the Cloud provider assigns a new IP address to the Instance. Claudie will never catch this and still issue reachability checks to the old IP, which may already be assigned
to another user of the Provider and thus may also pass reachability checks.

Discuss if Claudie should handle this by refreshing the node within terraformer service which should fetch the newly assigned IP to that VM. Or simply just assume and all of the templates used within claudie have long-live static IPs that are always assigned to that Instance.

Discuss also how exactly should the detection for this work, which is the most important part if decided to be implemented so that the reconciliation loop will not spam the refresh constantly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions