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
- Refactor helm installer to use a single meta chart install job
install job and config which use Helm v3 client.
- Use upstream helm client binary instead of using helm-client container
maintained by us. To verify checksum, helm_client_sha256 label is
introduced for helm_client_tag (or alternatively for URL specified
using new helm_client_url label).
- Default helm_client_tag=v3.2.1.
- Default tiller_tag=v2.16.7, tiller_enabled=false.
Story: 2007514
Task: 39295
Change-Id: I9b9633c81afb08b91576a9a4d3c5a0c445e0cee4
* remove user since it is controlled in the chart
and changed from 33 to 101
* use the latest chart v1.36.3 from stable
* use latest 0.32.0 controller image
story: 2006945
task: 39747
Change-Id: I6df49929cb8890f534afde185d56b7b6d70c691e
Signed-off-by: Spyros Trigazis <strigazi@gmail.com>
* Set requests.memory=256MiB for the nginx-ingress-controller pod
We decided to leave limits open as this will allow to support most
of the generic use cases.
* QoS from Guaranteed to Burstable
This will make that application and ingress starve each other,
both fighting for node resources for an optimal usage of CPU
* Set priority class so that pods can take priority on a node that
might have No CPU taint.
task: 37625
story: 2006945
Change-Id: Ibc77ea64ad47f1a400d040f419f38bf52b9f0141
Signed-off-by: Diogo Guerra <diogo.filipe.tomas.guerra@cern.ch>
The helm installer often quickly reaches the backoffLimit of 5. Increase
this to 10 so that there is a greater chance of successful installation.
Story: 2006765
Task: 37783
Change-Id: I5293c970bb1696f14c421fdf67abb495b4b8d666
Signed-off-by: Bharat Kunwar <brtknr@bath.edu>
Additioanlly, bumping up the Chart version to 1.24.7 without which the
ingress controller fails to deploy on 1.16.x.
Additionally, bump up nginx_ingress_controller_tag version to 0.26.1.
This is to ensure that we are running an up to date nginx ingress
controller with fixes for known CVEs.
Story: 2006853
Task: 37444
Change-Id: Ibf045a06d19b02095e19d9a21d14a91a39a3751c
Add an nginx based Ingress controller for Kubernetes.
The use case is to provide better support use cases which require either
L4 access or SSL passthrough, which lack proper support in Traefik.
Selection is done via the same label 'ingress_controller' with value
'nginx'. Deployment relies on the upstream nginx-ingress helm chart.
Change-Id: I1db2074fce9d43c03f479a6aaeb4f238d7101555
Story: 2005327
Task: 30255
Bharat Kunwar
Spyros Trigazis
Diogo Guerra
Bharat Kunwar
Ricardo Rocha