You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
krs scan
Scanning your cluster...
Cluster scanned successfully...
Extracted tools used in cluster...
The cluster is using the following tools:
+-------------+--------+-----------------------------+---------------+
| Tool Name | Rank | Category | CNCF Status |
+=============+========+=============================+===============+
| autoscaler | 5 | Cluster with Core CLI tools | unlisted |
+-------------+--------+-----------------------------+---------------+
| fluentbit | 4 | Logging and Tracing | unlisted |
+-------------+--------+-----------------------------+---------------+
krs recommend
Our recommended tools for this deployment are:
+-----------------------------+------------------+-------------+---------------+
| Category | Recommendation | Tool Name | CNCF Status |
+=============================+==================+=============+===============+
| Cluster with Core CLI tools | Recommended tool | k9s | unlisted |
+-----------------------------+------------------+-------------+---------------+
| Logging and Tracing | Recommended tool | elk | unlisted |
+-----------------------------+------------------+-------------+---------------+
helm install kubeview kubeview
NAME: kubeview
LAST DEPLOYED: Thu Jun 13 15:01:08 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
=====================================
==== KubeView has been deployed! ====
=====================================
To get the external IP of your application, run the following:
export SERVICE_IP=$(kubectl get svc --namespace default kubeview -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
echo http://$SERVICE_IP
NOTE: It may take a few minutes for the LoadBalancer IP to be available.
You can watch the status of by running 'kubectl get --namespace default svc -w kubeview'
krs scan
Scanning your cluster...
Cluster scanned successfully...
Extracted tools used in cluster...
The cluster is using the following tools:
+-------------+--------+-----------------------------+---------------+
| Tool Name | Rank | Category | CNCF Status |
+=============+========+=============================+===============+
| kubeview | 30 | Cluster with Core CLI tools | unlisted |
+-------------+--------+-----------------------------+---------------+
| | 3 | Cluster Management | unlisted |
+-------------+--------+-----------------------------+---------------+
| autoscaler | 5 | Cluster with Core CLI tools | unlisted |
+-------------+--------+-----------------------------+---------------+
| fluentbit | 4 | Logging and Tracing | unlisted |
+-------------+--------+-----------------------------+---------------+
@ajeetraina Check the cncf json that is created, if there is a name mismatch, it will show unlisted. As I am pulling from CNCF directly, I cannot edit the names in between, as they would be considered synthetic then.
I installed Nginx Pod on GKE workload by following this guide.
I was able to scan the GKE cluster successfully.
The text was updated successfully, but these errors were encountered: