feat(testkube): add custom labels and annotations through testkube-api helm chart

[manidharanupoju24]

Pull request description

This pull request addresses the issue: #695

Checklist (choose whats happened)

• breaking change! (describe)
• tested locally
• tested on cluster
• added new dependencies
• updated the docs
• added a test

Breaking changes

• N/A

Changes

• Added ability to specify labels and annotations for default job template via helm values.

Fixes

• N/A

[spkane]

Relates to: #695

[vsukhin]

job template structture van't be changed

[spkane]

@vsukhin, Can you provide a bit more detail on your thinking here?

Although this isn't our ideal approach, we did this precisely because it would not impact end users. Users can still override the job template. This makes it possible to pass helm values into the labels and annotations sections of the default job template when the user doesn't override the whole thing.

A better option might be to make it possible to pass in annotations and labels that one wants in the job templates to the operator as env vars and have it use standard go templating to apply them, but that requires touching the code, which we were trying to avoid for this particular workaround.

[vsukhin]

my main concern is that job template definition is splitted between template itself and configmap. so, it's no more self sufficient. I understand, that's a wroking hack, but it's not universal

[fulgas]

This is relevant when you are using linkerd as service mesh. The jobs will not terminate unless you disable the linkerd injection and that is done thru annotations.

[spkane]

@fulgas You might want to add that onto the core issue related to this: #695