Skip to content

Update configuration script to handle large cluster update case #198

@rjaini

Description

@rjaini

On large clusters a kubelet restart shows iptables exiting with status code 4
We should retry to handle such failures

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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