action #112511
closedcoordination #112454: [epic] Kubernetes testing
[Investigation] Check Helm deployment TTL and apply it to our test
0%
Description
In Helm test, we are currently installing the charts without TTL, and there could be a situation where the job is cancelled or killed right after the chart deployment and there is no cleanup performed. This can create left-overs in our K8S environments in the Public Cloud providers.
There are 2 solutions
1) Add cleanup of K8S pods in Public Cloud Watcher (might be needed anyways)
2) Investigate how to inject TTL information to the deployment https://github.com/jnummelin/pod-ttl-operator
3) Create own helm chart which will run a container which will exit after defined period of time
Option 1) is preferable, but if we can solve any potential left overs with option 2), then there is no rush in adding this functionality to pcw and we should add that TTL to the helm install command/configuration.
Updated by pdostal about 2 years ago
I moved the simple-job which just cats /etc/os-release into my helm chart which is basically a git repository.
Updated by pdostal almost 2 years ago
- Status changed from Workable to In Progress
Updated by pdostal almost 2 years ago
- Related to action #112517: Create our own Helm Chart for Helm tests added
Updated by pdostal almost 2 years ago
- Status changed from In Progress to Resolved
We now have our own chart which deploys only a job which ends itself so this is done.