Facing problems with non expected secrets

[betonetotbo]

This workaround was listing an unexpected secret and assuming it was an kubeconfig: secret/istio-reader-service-account-istio-remote-secret-token. The result was the cron fails:

Getting cluster name for remote cluster from secret/istio-reader-service-account-istio-remote-secret-token
Got cluster name: 
Getting kubeconfig for remote cluster from secret/istio-reader-service-account-istio-remote-secret-token
Got kubeconfig
Getting eastwestgateway's hostname
error: error loading config file "/tmp/kubeconfig": couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }

After inspecting the secrets, I found the ofensor and I was able to skip it by its type:

kubectl get secrets -n istio-system
NAME                                                     TYPE                                  DATA   AGE
cacerts                                                  Opaque                                4      5d5h
istio-ca-secret                                          istio.io/ca-root                      5      7d5h
istio-reader-service-account-istio-remote-secret-token   kubernetes.io/service-account-token   3      6d2h
istio-remote-secret-platform-arquitetura                 Opaque                                1      5d5h

Using the secret type, I was able to skip this invalid secret using the filter --field-selector type=Opaque

[markszabo]

LGTM, thank you very much for the contribution and the detailed explanation.