You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
There's often a need to cycle (restart) pods for various reasons, such as applying configuration changes, clearing memory leaks, or troubleshooting issues. Currently, Runtime lacks a built-in feature to easily perform this operation, requiring users to switch between our tool and kubectl or other Kubernetes management interfaces. This context switching reduces efficiency and can lead to errors.
Describe the solution you'd like
Given a Kubernetes cluster is connected to Runtime
When a user selects one or more pods in the tool's interface
Then the user should have an option to "Cycle Pods"
When the user chooses to cycle the selected pod(s)
Then Runtime Should
Gracefully terminate the selected pod(s)
Wait for Kubernetes to create new pod(s) to replace the terminated one(s)
Verify that the new pod(s) are in a running state
Provide real-time feedback on the cycling process
Log the action
Describe alternatives you've considered
Providing a direct link or documentation for kubectl commands for pod cycling. This doesn't solve the context switching problem.
Additional context
Consideration for the roles (RBAC) and permissions for who can execute any changes to the cluster need to be taken into account. This may warrant a design doc or ADR.
The text was updated successfully, but these errors were encountered:
adam-defenseunicorns
changed the title
Allow cycling of pods in Runtime
Allow cycling of pods in Runtime (consideration needed)
Oct 18, 2024
adam-defenseunicorns
changed the title
Allow cycling of pods in Runtime (consideration needed)
Allow cycling of pods in Runtime (permission consideration needed)
Oct 18, 2024
adam-defenseunicorns
changed the title
Allow cycling of pods in Runtime (permission consideration needed)
Allow cycling of pods (permission consideration needed)
Oct 21, 2024
Is your feature request related to a problem? Please describe
There's often a need to cycle (restart) pods for various reasons, such as applying configuration changes, clearing memory leaks, or troubleshooting issues. Currently, Runtime lacks a built-in feature to easily perform this operation, requiring users to switch between our tool and kubectl or other Kubernetes management interfaces. This context switching reduces efficiency and can lead to errors.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: