Without this, heat container agents using kubectl version
1.18.x (e.g. ussuri-dev) fail because they do not have the correct
KUBECONFIG in the environment.
Task: 39938
Story: 2007591
Change-Id: Ifc212478ae09c658adeb6ba4c8e8afc8943e3977
Expose autoscaler prometheus metrics on pod
port/portName name metrics (8085).
task: 37574
story: 2006765
Change-Id: Ieedd0f60625eb5a5ce50a3b4e7344cae37c377bf
Signed-off-by: Diogo Guerra <diogo.filipe.tomas.guerra@cern.ch>
hostNetwork: True ties the pod to the host ip:port.
When a CA update roll-out is triggered, the new pod cannot bind to the
port because it is already in use by the pod to be replaced, making the
new pod fail, and in consequence the update.
This patch removes this restriction
Story: 2006161
Task: 35670
Change-Id: I039b2ed91c9623883635bf9e72d85135f1bdae89
Signed-off-by: Diogo Guerra <dy090.guerra@gmail.com>
Using Node Problem Detector, Draino and AutoScaler to support
auto healing for K8s cluster, user can use a new label
"auto_healing_enabled' to turn on/off it.
Meanwhile, a new label "auto_scaling_enabled" is also introduced
to enable the capability to let the k8s cluster auto scale based
its workload.
Task: 28923
Story: 2004782
Change-Id: I25af2a72a7a960205929374d2300bd83d4d20960