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
This change adds upgrade action to allow users to upgrade Inspektor Gadget.
It aligns gadget version with Inspektor Gadget version to ensure compatibility.
Also, we setup the grpcruntime at runtime to ensure lastest kubeconfig is used
Signed-off-by: Qasim Sarfraz <[email protected]>
Copy file name to clipboardExpand all lines: docs/inspektor-gadget-usage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ Can you observe system calls for the pod my-pod in the default namespace for few
67
67
68
68
## Prerequisites
69
69
70
-
- A kubeconfig file that has access to the AKS cluster. You will need to restart the MCP server if you change the kubeconfig file.
70
+
- A kubeconfig file that has access to the AKS cluster.
71
71
- The tool requires Inspektor Gadget to be installed in the cluster. If you are running with `--access-level=readwrite` or more, the MCP server will automatically
72
72
install Inspektor Gadget (action `deploy` ) in the cluster otherwise you can follow the steps to install it manually: [Inspektor Gadget Installation](https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/logs/capture-system-insights-from-aks#how-to-install-inspektor-gadget-in-an-aks-cluster) or
73
73
use the official Helm chart: [Inspektor Gadget Helm Chart](https://inspektor-gadget.io/docs/latest/reference/install-kubernetes#installation-with-the-helm-chart):
0 commit comments