Changes between Version 4 and Version 5 of Tutorials/m0SDN/k8s


Ignore:
Timestamp:
Jul 12, 2023, 7:16:44 PM (17 months ago)
Author:
jlaxman
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/m0SDN/k8s

    v4 v5  
    11[[TOC(Documentation/f*, depth=3)]]
    22
    3 == Tutorial: Kubernetes Setup==
     3== Tutorial: Kubernetes Multi Node Setup==
    44Requirements:
    55
     
    1111
    1212----
     13Let’s take a look at this Kubernetes Multi-Node lab setup step-by-step and see how it is put together.
    1314
    14 In this tutorial, we will be using one of the sb9 nodes for setting up Kubernetes. However, sb(1-10) should also be capable for Kubernetes setup.
     15In this tutorial, we will be using one of the sb9 nodes for setting up Kubernetes. Any sb(1-10) should also be capable of Kubernetes setup.
    1516
    16 Make sure you have Ubuntu 20.04.5 (**baseline20.04.ndz**) or 22.04.2 (**ubuntu2204-beta.ndz**) LTS. To get the Ubuntu Version, follow these steps after ssh'ing into your console. Substitute for the image and node you want.
     17Make sure you have Ubuntu 20.04.5 (**baseline20.04.ndz**) or 22.04.2 (**ubuntu2204-beta.ndz**) LTS. To get the Ubuntu Version, follow these steps after ssh into your console. Substitute for the image and node you want.
    1718
    1819The below steps illustrate loading Ubuntu 20.04.5 LTS for node1-5 of sb1. For the sb1 console,
     
    3031}}}
    3132
    32 To verify if you have loaded your Ubuntu version properly, use this command after ssh into the node1-5 
     33To verify if you have loaded your Ubuntu version properly, use this command after ssh into the node1-5
    3334
    3435{{{#!shell
     
    123124
    124125=== Joining Worker Nodes to the Cluster ===
    125 Make sure you run till step 9[including] on the worker nodes and then
     126Make sure you follow till step 9[including] on the worker nodes, and then
    126127To join worker nodes to the Kubernetes cluster, run the `kubeadm join` command on the worker nodes that was outputted by the above `kubeadm init` command.
    127128
     
    132133}}}
    133134
     135To get the current status of nodes
     136{{{#!shell
     137root@node1-5:~# kubectl get nodes
     138}}}
     139
     140