Closed rsrchboy closed 6 months ago
Hello @rsrchboy! Thanks for the PR. Could you explain a bit more in depth what issue this tackles? So that I understand a bit better.
Importing this package causes common k8s client auth providers to be loaded and available to the built binary: OIDC, as well as GCP and Azure. Without it, those of us depending on those modes of authentication see this failure when invoking netfetch
:
$ netfetch scan default
Running native network policies scan...
Mode: CLI
Using default kubeconfig path: /home/cweyl/.kube/config
Error creating Kubernetes client: failed to create clientset: no Auth Provider found for name "oidc"
Error during Kubernetes native network policies scan: failed to create clientset: no Auth Provider found for name "oidc"
Is that sufficient? This is kinda a "gotcha!", as I suspect most of us assume that these common plugins would be loaded by the client libraries by default.
Importing this package causes common k8s client auth providers to be loaded and available to the built binary: OIDC, as well as GCP and Azure. Without it, those of us depending on those modes of authentication see this failure when invoking
netfetch
:$ netfetch scan default Running native network policies scan... Mode: CLI Using default kubeconfig path: /home/cweyl/.kube/config Error creating Kubernetes client: failed to create clientset: no Auth Provider found for name "oidc" Error during Kubernetes native network policies scan: failed to create clientset: no Auth Provider found for name "oidc"
Is that sufficient? This is kinda a "gotcha!", as I suspect most of us assume that these common plugins would be loaded by the client libraries by default.
Perfect. Thank you for the explanation, that is more than sufficient @rsrchboy. This will be included in the next release.
Merged into #134 to prepare for release.
...really, all known ones, but IIRC OIDC is the only one thus far.
This will address errors of the form: