Deployment of Litmus Edge Manager on Google Kubernetes Engine (GKE)

you can deploy litmus edge manager on google kubernetes engine (gke) before you begin a valid google cloud platform (gcp) project with permissions to create and manage kubernetes clusters see creating and managing projects & access control in gke for details familiarity with the google cloud console and cloud shell ensure the litmus google registry credential key file (e g , lem pull key file json ) is available and uploaded to your working environment to manually deploy litmus edge manager on google kubernetes engine (gke ), you will need to do the following step 1 setup your gke cluster in your gcp project step 2 connect to your cluster step 3 execute kubectl and helm commands step 4 access the litmus edge manager ui using the obtained ip address to jump to a specific section, refer to the table of contents on the right side and click the corresponding step step 1 setup your gke cluster in your google cloud platform (gcp) project to set up your gke cluster in your google cloud platform (gcp) project log in to your google cloud console select your gcp project , then navigate to kubernetes engine from the main menu you will land on the overview page of kubernetes engine click on clusters from the side menu and then create button to configure a new kubernetes cluster on the create an autopilot cluster page, configure the following cluster basics switch to standard cluster option (if not already selected) provide a name in lowercase (e g , gke cluster ) choose an appropriate region (e g , us central ) and select a zonal location type default pool configuration keep the default pool name or modify as needed keep the number of nodes at 2 for image type, select ubuntu with containerd ( ubuntu containerd ) choose a machine type with at least 2 cores and 16 gb memory network & security leave the default settings unless specific adjustments are required once configured, click create to initiate the cluster provisioning cluster creation may take several minutes note creating a cluster takes a few minutes, depending on the settings you choose please check the status or notifications for the latest information about our cluster step 2 connect to your cluster once your cluster is successfully created in the gke clusters page, click on the action button and then select connect you will be provided with the command line instructions to connect your local terminal or use the cloud shell option in gke copy the provided command and run it in your terminal, or click run in cloud shell to open the gke for this guide, we use the cloud shell in gke step 3 execute kubectl and helm commands with your connection established, use the following commands to deploy litmus edge manager from gke note keep your google registry credential key file in your workspace, as it's essential for authentication in deployment steps if you don't have the google registry credential key file in your workspace, click the action button in the panel menu then select upload a dialog box will appear, prompting you to upload the file click on file and then choose files to find the file on your computer after that, click upload to send it to gke 1\ execute the following command to create a namespace for litmus edge manager shell kubectl create namespace lem 2\ if required, create kubernetes secrets using helm to securely store credentials for example shell kubectl namespace lem create secret docker registry lem helm secret docker server=us east1 docker pkg dev \\ \ docker username= json key docker password="$(cat lem pull key json)" docker email=any\@email com 3\ install the litmus edge manager using helm adjust the version number (e g , 2 25 0 ) as needed shell helm install lem oci //us east1 docker pkg dev/litmus public/lem chart ga/lem version 2 25 0 namespace lem important notes the command initiates the pull of the necessary container images this process may take 1–2 minutes after the deployment is completed, wait approximately five minutes before applying the litmus edge manager(lem) urls and credentials instructions for accessing these urls and credentials will be printed out for you 4\ to get the litmus edge manager's external ip , run export lem url=$(kubectl get svc litmus edge manager n litmus edge manager o jsonpath='{ status loadbalancer ingress\[0] ip}') echo $lem url 5\ to get the username and password , run step 4 access the litmus edge manager ui using the obtained ip address see access to litmus edge manager docid\ w3uhzq4tsrh7oljhult0a for details note obtain the site license key from your litmus account executive to activate your license conclusion litmus edge manager is deployed and operational on your gke cluster you can now access the manager’s ui using the external ip address and proceed with any additional configuration, such as license activation, via the admin console review the below docu ments to learn more user profile administration docid\ xfog2xrprqinga9clszb