Merge pull request #592 from citrix/troubleshooting-update

updated the troubleshooting CIC section

Author: sreejithgs

docs/troubleshooting/troubleshooting-cic.md

@@ -1,15 +1,33 @@
 # Troubleshooting the Citrix ingress controller during runtime
 
+You can use te following tools available with Citrix ingress controller to help you in troubleshooting.
+
+## Kubectl plug-in for NetScaler
+
+NetScaler provides a [kubectl plug-in](https://github.com/netscaler/modern-apps-toolkit/tree/main/netscaler-k8s-plugin) to inspect ingress controller deployments and aids in troubleshooting operations. You can inspect the NetScaler configuration and related Kubernetes components using the subcommands available with this plug-in.
+
+Using the [support subcommand](https://github.com/netscaler/modern-apps-toolkit/tree/main/netscaler-k8s-plugin#support-command) you can get NetScaler (show techsupport) and ingress controller support bundle.
+
+You can collect and share the support bundle information with the support team for faster resolution.
+
+## Citrix ingress controller diagnostics Tool
+
+[Citrix ingress controller diagnostics tool](https://github.com/netscaler/modern-apps-toolkit/tree/main/cic_diagnostics_tool) is a simple shell script that collects information related to Citrix ingress Controller and applications deployed in the Kubernetes cluster.
+
+## Helpful commands for troubleshooting
+
 You can debug the Citrix ingress controller using the following methods:
 
-- Event based debugging
-- Log based debugging
+-  Event based debugging
+-  Log based debugging
+
+Providing the outputs of the commands in this section helps the support team in troubleshooting Citrix ingress controller.
 
-## Event based debugging
+### Event based debugging
 
 Events are Kubernetes entities which can provide information about the flow of execution on other Kubernetes entities.
 
-Event based debugging for the Citrix ingress controller is enabled at the pod level. To enable event based debugging, the RBAC cluster role permissions for the pod should be same as the cluster role permissions present in the [citrix-k8s-ingress-controller.yaml](https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/deployment/baremetal/citrix-k8s-ingress-controller.yaml) file.
+Event based debugging for the Citrix ingress controller is enabled at the pod level. To enable event-based debugging, the RBAC cluster role permissions for the pod should be same as the cluster role permissions present in the [citrix-k8s-ingress-controller.yaml](https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/deployment/baremetal/citrix-k8s-ingress-controller.yaml) file.
 
 Use the following command to view the events for the Citrix ingress controller.
 
@@ -38,9 +56,9 @@ In this example, the Citrix ADC has been deliberately made unreachable and the s
             Normal   Created    33m   CIC ENGINE, cic-vpx-functionaltest  SUCCESS: GET Default VIP from Citrix ADC:
             Warning  Created    17s   CIC ENGINE, cic-vpx-functionaltest  UNREACHABLE: Citrix ADC: Check Connectivity::<Citrix ADC IP>:80
 
-You can use the events section to check the flow of events within the Citrix ingress controller. Events provide information on the flow of events. For further debugging, you should check logs of the Citrix ingress controller pod.
+You can use the events section to check the flow of events within the Citrix ingress controller. Events provide information on the flow of events. For further debugging, you should check the logs of the Citrix ingress controller pod.
 
-## Log based debugging
+### Log based debugging
 
  You can change the log level of the Citrix ingress controller at runtime using the ConfigMap feature. For changing the log level during runtime, see the [ConfigMap](https://developer-docs.citrix.com/projects/citrix-k8s-ingress-controller/en/latest/configure/config-map/) documentation.