Use kube_master_ip for monitoring when no floating ip is used
This patch aims to fix clusters that uses only private network
and monitoring_enabled.
It was observed that:
- no floating ip, so the kube_master_external_ip is null
- because of that, the value that gets sent to the shell
for KUBE_MASTERS_PRIVATE is actually [null]
- this happens when deploying prometheus-operator
( label monitoring_enable=true )
Those topics above results in a cluster taking around 30
minutes to be completed until monitoring gives up configuring
endpoints.
Change-Id: I0fb4b2604f38bd3a325f82b1364b78ff17792c65
(cherry picked from commit 34f65582eb
)
This commit is contained in:
parent
9621d8e43d
commit
c664047829
|
@ -1339,7 +1339,7 @@ resources:
|
|||
template: {get_file: ../../common/templates/kubernetes/helm/prometheus-operator.sh}
|
||||
params:
|
||||
"${GRAFANA_ADMIN_PASSWD}": {get_param: grafana_admin_passwd}
|
||||
"${KUBE_MASTERS_PRIVATE}": {get_attr: [kube_masters, kube_master_external_ip]}
|
||||
"${KUBE_MASTERS_PRIVATE}": {get_attr: [kube_masters, kube_master_ip]}
|
||||
- get_file: ../../common/templates/kubernetes/helm/prometheus-adapter.sh
|
||||
- get_file: ../../common/templates/kubernetes/helm/ingress-nginx.sh
|
||||
- get_file: ../../common/templates/kubernetes/fragments/install-helm-modules.sh
|
||||
|
|
Loading…
Reference in New Issue