Skip to content

We need to always delete the kind cluster if we create kind cluster with Prow jobs #14

Open
@chizhg

Description

Currently when we run test flows with kind, we run kubetest2 kind --up --down which will also delete the kind cluster after the test flow finishes in the normal way. But if the Prow job is interrupted in the middle, the cluster will not be properly deleted thus will be causing memory leakage, as described in kubernetes-sigs/kind#303 (comment)

We should add a trap command to make sure the cluster can still be cleaned up even when the Prow job is interrupted.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions