What is the feature and why do you need it:
When loading the kube config, if any ConfigException is thrown it's caught and simply printed as an error message. This prevents any action being taken by the user when the exception is thrown. It also doesn't halt the application, which causes cascading errors.
Describe the solution you'd like to see:
Very simple fix:
|
except Exception as e: |
|
logging.error(str(e)) |
Should be:
except ConfigException as e:
raise ConfigException(e)
except Exception as e:
logging.error(str(e))
What is the feature and why do you need it:
When loading the kube config, if any ConfigException is thrown it's caught and simply printed as an error message. This prevents any action being taken by the user when the exception is thrown. It also doesn't halt the application, which causes cascading errors.
Describe the solution you'd like to see:
Very simple fix:
python/kubernetes/base/config/kube_config.py
Lines 519 to 520 in e0234d3
Should be: