Setting up Lens AppIQ is easy. We'll register, and install a few components inside your Kubernetes cluster when you connect it to Lens AppIQ and make sure that the CLI is set up with the correct API endpoint target.
Please open Lens AppIQ in your favorite browser and create an account by clicking the button "Sign in with Lens ID". Follow the instructions on the screen to create your own organization and access your dashboard
Next, connect a Kubernetes cluster to manage your apps using Lens AppIQ.
Once signed up, the first action needed is to connect a Kubernetes cluster of your choice. Lens AppIQ will need access to the Kubernetes API Endpoint.
In the left-hand navigation in Clusters, click the button + Connect Cluster.
Optionally enter a name for your cluster and click the button Generate Command. A Magic Link will be created for you to connect your Kubernetes cluster.
Copy and paste the
kubectl command into your terminal (while being within the desired cluster context) and execute the command.
$ kubectl apply -f "https://api.lenscloud.io/cluster-connect?authToken=..." namespace/shipa created secret/sh.helm.release.v1.shipa-agent.v1 created serviceaccount/shipa-agent created secret/shipa-agent created configmap/shipa-agent-config created clusterrole.rbac.authorization.k8s.io/shipa-agent-general created clusterrole.rbac.authorization.k8s.io/shipa-agent-autodiscovery-shipa-controller created clusterrole.rbac.authorization.k8s.io/shipa-agent-autodiscovery-helm created clusterrole.rbac.authorization.k8s.io/shipa-agent-containermetrics-busybody created clusterrole.rbac.authorization.k8s.io/shipa-agent-containermetrics-helm created clusterrolebinding.rbac.authorization.k8s.io/shipa-agent-general created clusterrolebinding.rbac.authorization.k8s.io/shipa-agent-autodiscovery-shipa-controller created clusterrolebinding.rbac.authorization.k8s.io/shipa-agent-autodiscovery-helm created clusterrolebinding.rbac.authorization.k8s.io/shipa-agent-containermetrics-busybody created clusterrolebinding.rbac.authorization.k8s.io/shipa-agent-containermetrics-helm created role.rbac.authorization.k8s.io/shipa-agent-general created role.rbac.authorization.k8s.io/shipa-agent-autodiscovery-shipa-controller created rolebinding.rbac.authorization.k8s.io/shipa-agent-general created rolebinding.rbac.authorization.k8s.io/shipa-agent-autodiscovery-shipa-controller created service/shipa-agent-api created deployment.apps/shipa-agent created
While our agents are deployed and the connection is established, you can monitor the process locally by running the command
kubectl get pods -n shipa -w into your terminal. Wait until all pieces are in a "Running" status.
$ kubectl get pods -n shipa NAME READY STATUS RESTARTS AGE shipa-agent-5879fb7954-wtp44 1/1 Running 0 3m9s shipa-busybody-rgdgk 1/1 Running 0 2m53s shipa-controller-6ccf95854d-cfdtp 1/1 Running 0 2m56s
At this point in time, you should see your cluster in the dashboard in a
Connecting state. Hover over the status dropdown to see which pieces of the control plane are Running already and which ones are still Pending to be installed.
Once the installation of the control plane is finished, your cluster should appear on the Cluster list page with a
Now you are ready to manage your applications using Lens AppIQ.
After you connect your cluster, Lens AppIQ scans your cluster and lists all your applications across all namespaces under its Application menu.
Click on an Application and click on "View Map," and you can take a look at your workload's dependencies in a Lens AppIQ Application Map.
You are now well on your way to managing your applications: e.g., you can troubleshoot your applications by looking at their metrics, logs, setup webhooks, attach policies to specific namespaces, and more.
A great next step would be to install the Lens AppIQ CLI e.g Install Lens AppIQ Client
brew tap shipa-corp/cli brew install lapps-cloud-cli lapps login
Lens AppIQ OAuth/SSO CLI Authentication
To wire the CLI to SSO, head to Settings then your token for Single Sign On CLI
lapps sso login <token>
Updated 3 months ago