Cortex Cloud: How to gather logs using Ktool for EKS/AKS/GKE/Openshift clusters when a Kubernetes Connectors is deployed.

This article will show you how to use the Internal ktool created by our backend engineering team to gather logs that'll help engineering and TAC engineers debug your Kubernetes Konnector issues. 

Cortex Cloud 1.3 release and above. 

Current Konnector Version: 2.1.48

Steps to use the internal tool to gather logs:

1. 

kubectl get cronjob -n panw (This is to validate the job-orchestrator name)

2. 

kubectl create job --from=cronjob/job-orchestrator test-job -n panw (Our engineering asks if a test-job can be ran before collecting the ktool)

3. 

kubectl get pods -n panw -l job-name=test-job (Monitor the status of the test-job and wait for it to complete)

4.

curl -fsSL https://raw.githubusercontent.com/PaloAltoNetworks/ktool/main/install.sh | bash

5. 

kubectl ktool collect-logs -n panw

Note: For Openshift run the following command (the space is not by mistake)

oc  ktool collect-logs -n panw

6. 
Let it run and complete with the output it generates: ./tsf-konnector-<timestamp>.tar.gz

Lastly, please attach the document to the support case at your earliest convenience so that our engineering and TAC team can analyze.

Please run the following commands if customer is not able to use ktool:

kubectl patch configmap konnector-globals -n panw --type merge -p '{"data":{"UPLOAD_LOG_LEVEL":"DEBUG"}}'

kubectl rollout restart deployment cortex-manager -n panw