Kubernetes Installation

5 min

before you begin get access to a configured kubernetes cluster get access to persistentvolumeclaim (pvc) learn more about persistent volumes from the kubernetes documentation get administrative permissions to run the kubectl command line tool depending on the specific requirements of your environment, you may need to get access to a storage class learn more about storage classes from the kubernetes documentation step 1 launch a litmus edge on kubernetes to launch a litmus edge on kubernetes cluster 1 open a command prompt terminal (ctrl+r) 2 execute the following commands to create a new kubernetes namespace bash kubectl create namespace le prodkubectl create namespace le prod the command creates a namespace named le prod note le prod should be changed to an isolated namespace to suit deployment best 3 copy the following litmus edge deployment file and save it to litmusedge deployment yaml file \# create serviceaccount apiversion v1 kind serviceaccount metadata name litmusedge docker namespace le prod labels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance \ \# create pvc kind persistentvolumeclaim apiversion v1 metadata name litmusedge data namespace le prod labels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance spec accessmodes \ "readwriteonce" resources requests storage "10g" \ \# create service apiversion v1 kind service metadata name litmusedge docker namespace le prod labels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance spec type clusterip ports \ port 443 targetport https protocol tcp name https selector app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance \ \# create deployment apiversion apps/v1 kind deployment metadata name litmusedge docker namespace le prod labels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance spec replicas 1 selector matchlabels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance template metadata labels app kubernetes io/name litmusedge docker app kubernetes io/instance litmusedge instance spec serviceaccountname litmusedge docker securitycontext {} containers \ name litmusedge docker securitycontext capabilities add \ net admin image "litmusedge azurecr io/litmusedge std docker\ latest" imagepullpolicy ifnotpresent ports \ name https containerport 443 protocol tcp volumemounts \ mountpath /var mountpropagation name litmusedge data subpath subpathexpr resources requests cpu 1 memory 1024mi limits cpu 4 memory 4096mi volumes \ name litmusedge data persistentvolumeclaim claimname litmusedge data 4 execute the following command to deploy a litmus edge kubernetes cluster using the deployment file from step 4 bash kubectl apply f litmusedge deployment yaml namespace le prodkubectl apply f litmusedge deployment yaml namespace le prod refer to the command parameters f litmusedge deployment yaml uses the file litmusedge deployment yaml for deployment this should not be changed namespace le prod sets le prod to be the deployment that kubernetes will use special and additional considerations litmus edge can function in both single and multi kubernetes node clusters, and can support various networking modes your kubernetes admin has the responsibility to configure proper networking adjust cpu/ram/storage for the kubernetes cluster as needed storage should be set to at least 10gb scale additional computing resources when using litmus edge features that require high computing power, such as plc drivers, integrations, and flows review kubernetes official documentation https //kubernetes io/docs/home/ for best practices ensure credentials are stored properly with kubernetes management net admin permissions are required step 2 log in to litmus edge see access the litmus edge web ui docid\ hqybg3t5t6irowc2rbbhf for details on logging in see access the terminal user interface docid\ trevmtf8z 5yhmypnmo c for instructions on how to navigate and log in for the first time note to identify the port configured by the admin, use the following command kubectl get svc n le prod