Copy the labels to the underlying template even if it does not have any #737
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
kube-burner copies the labels of its created objects into the template of the underlying object (e.g. pod template of a deployment). These labels are then used in other places in the code. For example, metrics measurements rely on the existence of the
kube-burner-runid
label on the pod (or VMI in case of VMs).In the original code, the labels were copied only if the labels field already existed.
With these fix, for specific kinds, the labels are copied even if none were added.
Related Tickets & Documents