Update k8s array system retries max value

[hamersaw]

TL;DR

Currently the k8s array plugin uses the interruptible threshold for the maximum value in the bitarray tracking system failures for map task subtasks. If the bitarray attempts to store a value over it's maximum configured value it results in a panic (rather than throwing an error). Therefore, a panic may occur if the number of system retries exceeds the interruptible threshold. This PR uses the maximum number of retries as the maximum value in the system retries bitarray and therefore fixes the panic.

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

^^^

Tracking Issue

fixes flyteorg/flyte#2788

Follow-up issue

NA

[codecov]

Codecov Report

Merging #284 (edd3614) into master (e863c76) will not change coverage.
The diff coverage is 100.00%.

❗ Current head edd3614 differs from pull request most recent head cb37557. Consider uploading reports for the commit cb37557 to get more accurate results

@@           Coverage Diff           @@
##           master     #284   +/-   ##
=======================================
  Coverage   63.28%   63.28%           
=======================================
  Files         145      145           
  Lines        9264     9264           
=======================================
  Hits         5863     5863           
  Misses       2866     2866           
  Partials      535      535           

Flag	Coverage Δ
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
go/tasks/plugins/array/k8s/management.go	57.21% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.