Skip to content

Kill a pod from the GitLab UI

Release notes

You would need to restart a failing pod. Until now, you had to leave GitLab, open another tool that can connect to the cluster, kill the pod there, and wait for the new pod to come up. GitLab now has built-in support for killing pods, allowing you a smoother troubleshooting experience around your Kubernetes clusters.

Problem to solve

As an Application Operator, I want to kill a pod, so that it can be restarted and run smoothly.

Proposal

Add an action button to the pod list and detail views on the GitLab K8s UI to "Kill" the pod. Ask for a confirmation.

Intended users

Feature Usage Metrics

  • event: kill_pod_clicked
    • attributes to track: environment_id, agent_id (project id, user id are tracked automatically)

Metrics:

  • MAU killing pods
  • Monthly environments killing pods
  • Frequency of pods being killed by environment (How often do users kill a pod for the same agent)
  • Monthly projects killing pods

Does this feature require an audit event?

Yes.

Proposed Design

List (With and Without Dropdown Open) Details Drawer (With and Without Tooltip Open) Confirmation Modal
Screenshot_2024-07-05_at_2.41.07_PM
Screenshot_2024-07-05_at_2.42.53_PM 		Screenshot_2024-07-05_at_2.41.14_PM
Screenshot_2024-07-05_at_2.42.19_PM 		Screenshot_2024-07-05_at_2.41.21_PM

Implementation proposal

For the pods table:

  1. Add a new column for other actions to the workload_table component.
  2. Use disclosure dropdown for the actions list.

For the drawer:

  1. Add a new section for actions to the workload_details component.
  2. Use GlButton with the remove icon.

Common:

  1. Add a confirmation modal for the pod deletion
  2. Add a mutation to call the delete pod API
Edited by Anna Vovchenko