Skip to content

Resolve "Use kubectl port-forward instead of SSH tunnel"

Closes #34 (closed)

It's possible that the set-port-forward script does work for @davor whereas the old SSH tunnel script apparently didn't work.

To use it, you'll need kubectl access to the cluster:

  1. Install kubectl (available through snap for linux, I don't know how to install it on Windows)

  2. Download the kubeconfig: scp kube_config_init.yaml

  3. Set kubectl to use the kubeconfig. I know how to do it in a shell: export KUBECONFIG=$PWD/kube_config_init.yaml. Could be different on Windows too

  4. Test if it works:

    kubectl get ingress -n stackspin

    Should return something like:

    NAME                                 CLASS    HOSTS                             ADDRESS         PORTS     AGE
    hydra-public                         <none>     80, 443   39d
    dashboard                            <none>   80, 443   150d
    kube-prometheus-stack-grafana        <none>   80, 443   108d
    kube-prometheus-stack-alertmanager   <none>   80, 443   108d
    kube-prometheus-stack-prometheus     <none>   80, 443   108d
  5. Run the script to forward ports of the services to your local setup:


    No arguments needed: the kubectl connection already exists, so we know which cluster you want to use. The namespace defaults to stackspin, because nobody has a different namespace anymore.

Edited by Maarten de Waard

Merge request reports