Boundary connect kube - How do I run "kubectl get nodes"?

How do I run kubectl commands using the kube built-in wrapper for boundary connect?

i.e. kubectl get nodes from the target host.

boundary connect kube  -target-id <target-id>
kubectl controls the Kubernetes cluster manager.

 Find more information at:

Basic Commands (Beginner):
  create        Create a resource from a file or from stdin.
  expose        Take a replication controller, service, deployment or pod and expose it as a new Kubernetes Service
  run           Run a particular image on the cluster
  set           Set specific features on objects

Basic Commands (Intermediate):
  explain       Documentation of resources
  get           Display one or many resources
  edit          Edit a resource on the server
  delete        Delete resources by filenames, stdin, resources and names, or by resources and label selector

Deploy Commands:
  rollout       Manage the rollout of a resource
  scale         Set a new size for a Deployment, ReplicaSet or Replication Controller
  autoscale     Auto-scale a Deployment, ReplicaSet, or ReplicationController

Cluster Management Commands:
  certificate   Modify certificate resources.
  cluster-info  Display cluster info
  top           Display Resource (CPU/Memory/Storage) usage.
  cordon        Mark node as unschedulable
  uncordon      Mark node as schedulable
  drain         Drain node in preparation for maintenance
  taint         Update the taints on one or more nodes

Troubleshooting and Debugging Commands:
  describe      Show details of a specific resource or group of resources
  logs          Print the logs for a container in a pod
  attach        Attach to a running container
  exec          Execute a command in a container
  port-forward  Forward one or more local ports to a pod
  proxy         Run a proxy to the Kubernetes API server
  cp            Copy files and directories to and from containers.
  auth          Inspect authorization
  debug         Create debugging sessions for troubleshooting workloads and nodes

Advanced Commands:
  diff          Diff live version against would-be applied version
  apply         Apply a configuration to a resource by filename or stdin
  patch         Update field(s) of a resource
  replace       Replace a resource by filename or stdin
  wait          Experimental: Wait for a specific condition on one or many resources.
  kustomize     Build a kustomization target from a directory or a remote url.

Settings Commands:
  label         Update the labels on a resource
  annotate      Update the annotations on a resource
  completion    Output shell completion code for the specified shell (bash or zsh)

Other Commands:
  api-resources Print the supported API resources on the server
  api-versions  Print the supported API versions on the server, in the form of "group/version"
  config        Modify kubeconfig files
  plugin        Provides utilities for interacting with plugins.
  version       Print the client and server version information

  kubectl [flags] [options]

Use "kubectl <command> --help" for more information about a given command.
Use "kubectl options" for a list of global command-line options (applies to all commands).
1 Like

Looks like I just had to run:

boundary connect kube -target-id ttcp_t12345 -- get nodes


Yep! boundary connect kube uses the same format as boundary connect and the other helper commands – anything after the double-dash gets passed through to the executed command.

1 Like

Hey Jeff,

So now that I’m connected to kubernetes.

How would I go about limiting this specific user to only running commands within a specific namespace?

Are kuberentes roles set in the Grants, or do I have to pass in a –kubeconfig=<path to .conf file for the cluster> argument, while somehow preventing users from using kube connect without a kubeconfig argument?
boundary connect kube -target-id ttcp_t12345 -- get nodes
boundary connect kube -target-id ttcp_t12345 -- --kubeconfig=~/admin.conf get nodes

1 Like