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
For the VelaQL, we should keep it read-only. Restarting or deleting the pod should add a standalone API, and it is beneficial to access control. But, the API could depend on VelaQL to discover the target resources.
I wanted to clarify the features outlined in issues #718 and #666.
Issue #718 focuses on adding the ability to restart (delete) a specific pod in Velaux.
Issue #666 aims to implement functionality similar to kubectl rollout restart deployment mydeploy, allowing for the restart of entire deployments.
Do we need to implement both features, or is there a specific priority for one over the other? Your insights would be greatly appreciated!
Is your feature request related to a problem? Please describe.
In K8s, restart a pod is actually delete it, we can just delete it using velaql mechanism, create a velaql view and invoke the velaql API in the UX.
In the UI side, we can add button like below:
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: