Skip to content
Railgrid Docs
Sections
Open console

Enter a topic to search documentation.

    railgrid connect

    Point kubectl at a Kubernetes edge

    Synopsis

    Add a kubeconfig context named railgrid-<edge> for the edge’s Kubernetes API (reached through the hub’s edge proxy with your hub credentials) and make it the current context, so plain kubectl talks to that cluster:

    Terminal
    railgrid connect my-cluster
kubectl get nodes
railgrid disconnect            # back to the hub workspace

    Without an argument an interactive picker lists the connected clusters. The context stays in your kubeconfig; switch between edges with ‘kubectl config use-context railgrid-<edge>’ or connect again.

    Terminal
    railgrid connect [<edge>] [flags]

    Options

    TEXT
      -h, --help   help for connect

    Inherited options

    TEXT
          --insecure-skip-tls-verify   Skip TLS certificate verification when talking to the hub
      --kubeconfig string          Path to the kubeconfig file (default: $KUBECONFIG, then ~/.kube/config)

    See also

    • railgrid — railgrid: an open-source control plane for platform teams