• Created by Unknown User (zw738), last updated by Unknown User (zl469) on May 21, 2025 2 minute read

Connect to the Server

  1. Generate EC2 Key (skip this step if you have EC2 private SSH key locally)  
    1. ssh into / (open via aws ec2 console) the EC2 ubuntu VM (DIAPER-production-key.pem is in the box folder diaper confidential ask Liz for access), create the new user (if not yet created)
      sudo adduser newuser
    2. switch to the new user
      sudo su - newuser
    3. generate key by using
      ssh-keygen
    4. Hence, we get id_rsa (private key) & id_rsa.pub (public key)
    5. Store into the folder in home/accountuser/.ssh
      mv id_rsa.pub authorized_keys 
    6. exit to ubuntu:
      exit
    7. copy the private key into ubuntu's home for download (temporary), use 'chmod' to change file's permission if necessary:
      sudo cp /home/newuser/.ssh/id_rsa /home/ubuntu/
    8. Download id_rsa to local 
      scp -i "DIAPER-production-key.pem" ubuntu@ec2-3-239-18-167.compute-1.amazonaws.com:/home/ubuntu/id_rsa ./
  2.  Connect to EC2:
    1. ssh -i  <private.key> -L 6445:localhost:6443 username@ssh.diaper-project.com
      1. -L mean to forward server's port to local, because Kubernetes exposes port 6445, we would like to forward it to localhost:6443.

      2.  Username is your NetID. An admin account holder should be able to create the linux account for you.

    2. If permission error

      sudo chmod 600 private.key
    3. You should see a pop-up looks like this, which means that you have already connected to the server.

Connect to Kubernetes

Reminder, before connecting to the server. You need to ask the admin for a server token. 

  1. Install Kubernetes by Docker (you might want to use Docker to build images), check out Install and turn on Kubernetes
  2. There are various UI explorers for Kubernetes. Such as k9s, check out Install (k9scli.io).
  3. Add the server cluster credentials in the Kubernetes config file. (In Mac, config file is located in ~/.kube). The configuration is as follows:
    1. apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJlRENDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdGMyVnkKZG1WeUxXTmhRREUzTURjeE56SXpNRFl3SGhjTk1qUXdNakExTWpJek1UUTJXaGNOTXpRd01qQXlNakl6TVRRMgpXakFqTVNFd0h3WURWUVFEREJock0zTXRjMlZ5ZG1WeUxXTmhRREUzTURjeE56SXpNRFl3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFSeG5lcFhxd1oxSUNGcXBrcmNqNkNIdDlxK3daSUV6N093ajM5VXJmRnoKTHBBS2tpUzhpS2NIRGNHMTZiazFjaEhzbVdTLzZjV0ptZm5ueEs3cTg2WDNvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVUpsRGJlajRVa2IyV0ZVRjBDREd2CnNrWkUzOG93Q2dZSUtvWkl6ajBFQXdJRFNRQXdSZ0loQUxKelRCZTQyZFZtMmtTWUJWQW5TZW05bWw1TSt1NVcKQVkya1cyamcvMy80QWlFQXdhMTlENk1IcThPTS9pMTlSWitXYUxrdkJYV3Uwb1MwWmJCV2UzdFJvY2c9Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
    server: https://127.0.0.1:6445
  name: diaper-server
contexts:
- context:
    cluster: diaper-server
    user: <Kubernetes service account name>
  name: diaper-server
current-context: diaper-server
kind: Config
preferences: {}
users:
- name: <Kubernetes service account name>
  user:
    token: <Kubernetes service account token>
  4. Connect to the Kubernetes cluster using the command
    1. k9s
  5. then you have
    2. If you don't see all pods running, it is probably because you're viewing a specific namespace. You can simply press '0' to view pods in all namespaces.
    3. To navigate between Services, Deployments, or Pods, you can type 
      :services       or       :deployments       or       :pods
    4. To port-forward a pod, type shift+F.  To view the log, type l. To kill a pod, type ctrl+k.... You can always view these commands by typing ?(question mark).

More k9s Tutorial: derailed/k9s: 🐶 Kubernetes CLI To Manage Your Clusters In Style! (github.com)

  • No labels