Currently, we are able to get logs from executed Actions via Capact CLI, so user doesn't need to use the kubectl and get a proper pods names.
Both options work:
get the latest logs from the Action execution
stream logs from the Action execution
However, the first implementation was done via direct call to K8s cluster. This should be abstracted. We can implement a query and subscription on GraphQL endpoint or create a separate REST endpoint just for streaming logs.
Reason
The current solution requires a valid kubeconfig to a k8s cluster. It's not generic solution and additionally it's easy to use different cluster that the one configured by CLI login.
Use cases
System User — I want to have a single point of authorization to my cluster via Gateway. All commands should work in a consistent way.
Description
Currently, we are able to get logs from executed Actions via Capact CLI, so user doesn't need to use the
kubectland get a proper pods names.Both options work:
However, the first implementation was done via direct call to K8s cluster. This should be abstracted. We can implement a query and subscription on GraphQL endpoint or create a separate REST endpoint just for streaming logs.
Reason
The current solution requires a valid kubeconfig to a k8s cluster. It's not generic solution and additionally it's easy to use different cluster that the one configured by CLI login.
Use cases