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
Assuming bi-directional management is interesting for our users, we should potentially add bi-directional service management.
This would allow support for the following operations:
List services - kubectl get svc -A, kubectl get svc
Listing services across all namespaces or the default namespace will include a service for each container created via docker run... that expose at least one port. These will default to hostPort type services.
Inspect a service - kubectl get svc/container-name, kubectl describe svc/container-name
Allows you to inspect a service associated to a container created via docker run...
Delete a service - kubectl delete svc/container-name
Allows a user to remove any port exposed on a container created via docker run...
The text was updated successfully, but these errors were encountered:
Follow-up on #79
Assuming bi-directional management is interesting for our users, we should potentially add bi-directional service management.
This would allow support for the following operations:
kubectl get svc -A
,kubectl get svc
docker run...
that expose at least one port. These will default to hostPort type services.kubectl get svc/container-name
,kubectl describe svc/container-name
docker run...
kubectl delete svc/container-name
docker run...
The text was updated successfully, but these errors were encountered: