Helm configurable request limit

[j-zimnowoda]

Is your feature request related to a problem? Please describe. Looks like our deployment pipeline overloads Kubernetes-api, while running the otomi apply command.

Error: Kubernetes cluster unreachable: Get "https://10.0.0.1:443/version": dial tcp 10.0.0.1:443: i/o timeout

Describe the solution you'd like A clear and concise description of what you want to happen. We can mitigate that issue by setting Helm burst limit, which restrict number of requests per second. The default is 100, but we could decrease it to 50.

TODO:

• set burstLimit in helmDefaults at the env.gotmpl file
• update helm version 3.10.3 in tools/Dockerfile
• release new tools image and use it as a base in otomi.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

[j-zimnowoda]

Google has a rate limit ~50 req / second

[j-zimnowoda]

Google has rate limit ~50 req / second

[j-zimnowoda]

Hey team! Please add your planning poker estimate with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @merll