Handle timeout loading conf secret

[borigas]

On my AKS cluster, requests to the k8s api sometimes timeout. Currently, the behavior of a timeout loading the conf secret results in generating a new cert without the previous configuration. That results in potentially bumping up on rate limits because cert renewal dates are never available and also rotates public/private keys, which can affect certificate pinning.

To fix, I'm exiting the script if the status code was not set when loading the conf secret. If you have a better way to handle, please let me know