Decide how to handle CAPD containers being stopped

[stmcginnis]

Detailed Description

If we deploy a cluster using CAPD, then stop one of the containers after deployment, there is no kind of remediation that happens and depending on which container, there may only be some errors logged about failed connections.

We get a list of the containers present, but it doesn't appear we check the container status to see that the container has exited.

We should determine the appropriate way to react to these scenarios to make sure things behave as a user would expect.

Anything else you would like to add:

See discussion in #5021 for more context.

/kind feature

[fabriziopandini]

+1 to surface a condition, but I would defer to the user remediation because stopping container might be useful to test remediation, easing memory pressure, etc.

/milestone v0.4

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[fabriziopandini]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[fabriziopandini]

/remove-lifecycle rotten
/milestone Next

[fabriziopandini]

/close

This is not a problem for CAPD usage in E2E tests/quick start. We can re-open if there is demand for other use cases

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

/close

This is not a problem for CAPD usage in E2E tests/quick start. We can re-open if there is demand for other use cases

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.