Add support for Kaniko flag --image-fs-extract-retry

[RabidFire]

Hi! My first pull request here 👋

Related:

• PR I used for reference: added support for kaniko pushretry #6211
• PR that added the flag to Kaniko: Retry extracting filesystem from image kaniko#1685

Description
Adds support for a newly introduced Kaniko flag, --image-fs-extract-retry. This is important for GCB users, as builds fail often and need to be retried by hand without this flag.

User facing changes
New configuration option imageFSExtractRetry in the kaniko section.

Side Note: I wanted to play with the --cache-copy-layers flag as well, but this is also missing. Perhaps the previous architecture where the user could add additionalFlags themselves was better (changed here). It would definitely be useful to be able to add custom flags without waiting for a skaffold release.

[codecov]

Codecov Report

Merging #6380 (7d1ea3b) into main (84367d9) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #6380   +/-   ##
=======================================
  Coverage   70.38%   70.39%           
=======================================
  Files         499      499           
  Lines       22722    22724    +2     
=======================================
+ Hits        15994    15996    +2     
  Misses       5685     5685           
  Partials     1043     1043           

Impacted Files	Coverage Δ
pkg/skaffold/schema/latest/v1/config.go	62.16% <ø> (ø)
pkg/skaffold/build/kaniko/args.go	95.65% <100.00%> (+0.09%)	⬆️
pkg/skaffold/docker/parse.go	87.39% <0.00%> (-0.85%)	⬇️
pkg/skaffold/util/tar.go	65.51% <0.00%> (+2.29%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84367d9...7d1ea3b. Read the comment docs.

[gsquared94]

looks good to me!

[gsquared94]

Perhaps the previous architecture where the user could add additionalFlags themselves was better (changed here). It would definitely be useful to be able to add custom flags without waiting for a skaffold release.

@tejal29 should we bring back additionalFlags to support arbitrary flags in addition to the typed ones?

[tejal29]

Perhaps the previous architecture where the user could add additionalFlags themselves was better (changed here). It would definitely be useful to be able to add custom flags without waiting for a skaffold release.

@tejal29 should we bring back additionalFlags to support arbitrary flags in addition to the typed ones?

we should definitely discuss this and keep is same across all tool config (docker, kubectl, etc)