I've been wondering myself how to install an Argo Rollouts plugin for kubectl on Windows. Turns out, I had to rename the downloaded file to match what kubctl was actually expecting and place it anywhere on the PATH. Here's what I did
The plugin downloaded file was originally named
kubectl-argo-rollouts-windows-amd64- I've renamed it to justkubectl-argo-rollouts.exeI've then placed the renamed plugin file along with the
kubeclt.exe(since I've been originally using a temp AKS cluster, that was.auzre-kubectlfolder in my Windows user's profile rootRan the the
kubectl plugin listcommand and got the following:The following compatible plugins are available:C:\Users\mysuernamehere\.azure-kubectl\kubectl-argo-rollouts.exeFinally, verified the plugin is indeed recognized by running
kubectl argo rollouts version
Hope this helps!
Answer from MasterRadollo on Stack OverflowI've been wondering myself how to install an Argo Rollouts plugin for kubectl on Windows. Turns out, I had to rename the downloaded file to match what kubctl was actually expecting and place it anywhere on the PATH. Here's what I did
The plugin downloaded file was originally named
kubectl-argo-rollouts-windows-amd64- I've renamed it to justkubectl-argo-rollouts.exeI've then placed the renamed plugin file along with the
kubeclt.exe(since I've been originally using a temp AKS cluster, that was.auzre-kubectlfolder in my Windows user's profile rootRan the the
kubectl plugin listcommand and got the following:The following compatible plugins are available:C:\Users\mysuernamehere\.azure-kubectl\kubectl-argo-rollouts.exeFinally, verified the plugin is indeed recognized by running
kubectl argo rollouts version
Hope this helps!
I think only .exe file extensions are considered as executables by kubectl when it searches for plugins in the $PATH when running in Windows environment. I tested by creating a simple HelloWorld App as a single file executable, added it to my system's $PATH and it got picked up and executed correctly.