-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Rob Herley edited this page Mar 5, 2019
·
2 revisions
Node | Type | IP | DNS |
---|---|---|---|
kub1 | master | 155.246.89.116 | kub1.srcit.stevens-tech.edu |
kub2 | worker | 155.246.89.116 | kub2.srcit.stevens-tech.edu |
kub3 | woker | 155.246.89.116 | kub3.srcit.stevens-tech.edu |
They are protected by the same LDAP/Kerberos used by Stevens Linux Lab
Connect to each of the nodes like so:
$ ssh <user>@<node>.srcit.stevens-tech.edu
It may be easier to use a script like so:
# in your shell's rc file
alias lab='function _lab(){ ssh "$USER@$1.srcit.stevens-tech.edu" };_lab'
$ lab kub1 # or kub2, kub3, etc
First, obtain the kubeconfig from Rob and place it in $HOME/.kube/config
, then export in in your .bashrc
or .zshrc
as so:
export KUBECONFIG=/home/$USER/.kube/config
Ensure you are connected to the Stevens network via VPN, then you should be able to run commands against the cluster with kubectl
:
$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
kub1 Ready master 10h v1.13.4
kub2 Ready <none> 10h v1.13.4
kub3 Ready <none> 10h v1.13.4