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
It would ideal to allow for tracking of assets in Kubernetes. This would further extend the exec command to get a shell into one or more containers (or all containers in a pod with tmux).
This is a larger issue that hasn't been fully worked out, so it could probably be broken into further smaller issues/PRs, but here's a start:
add a new Inventory class that inherits from and further implements the InventorySource (in bridgy/inventory/source.py) and put under bridgy/inventory/kubernetes.py.
Add a new InstanceType (something like KUBERNETES or K8S)
The definition of Instance may need to change or take a nested payload with inventory-specific items.
It would ideal to allow for tracking of assets in Kubernetes. This would further extend the
exec
command to get a shell into one or more containers (or all containers in a pod with tmux).This is a good starting point for how the mechanisms of streaming to/from the container (seems more kosher than wrapping kubectl): https://github.com/kubernetes-client/python/blob/master/examples/exec.py
The text was updated successfully, but these errors were encountered: