magnum/magnum
Feilong Wang d224999cb0 Improve log of k8s health status check
When the k8s cluster is created in a private network without
FIP and without a LB FIP, the cluster is not reachable by Magnum
control plane. For this case, the cluster health status is unknown
for Magnum and Magnum should not connect the cluster to avoid
unnecessary logs.

Task: 36187
Story: 2006383

Change-Id: Ibb589ec51f91f05a334c907560ef5fe57cbfbffb
2019-10-01 18:29:16 +00:00
..
api ng-8: APIs for nodegroup CRUD operations 2019-09-26 08:45:57 +00:00
cmd ng-8: APIs for nodegroup CRUD operations 2019-09-26 08:45:57 +00:00
common ng-8: APIs for nodegroup CRUD operations 2019-09-26 08:45:57 +00:00
conductor ng-8: APIs for nodegroup CRUD operations 2019-09-26 08:45:57 +00:00
conf [fedora atomic k8s] Add boot from volume support 2019-09-20 05:00:29 +00:00
db ng-6: Add new fields to nodegroup objects 2019-09-25 12:26:00 +00:00
drivers Improve log of k8s health status check 2019-10-01 18:29:16 +00:00
hacking Fix typo in magnum/hacking/checks.py for consistency 2017-06-16 15:43:27 +08:00
objects Improve log of k8s health status check 2019-10-01 18:29:16 +00:00
service Add information about the cluster in magnum event notifications 2019-07-29 11:23:42 +03:00
servicegroup Trivial code cleanups 2018-10-02 19:41:34 +00:00
tests Improve log of k8s health status check 2019-10-01 18:29:16 +00:00
__init__.py Initial commit from github (squashed) 2014-11-18 09:23:37 -05:00
i18n.py Remove log translations 2017-03-30 17:05:10 +08:00
version.py Remove coding:utf-8 2015-08-03 23:28:22 +08:00