Spike: Investigate recommendations we're ignoring from kube-score

Follow-up suggestion

The following discussion from !4047 (merged) should be addressed:

• @stanhu started a discussion: (+4 comments)

  I do wonder if we actually want to address the warnings here. 😄

Description

We've introduced kube-score linting to our chart, initially to detect duplicated environment variables being set. Therefore, we've included numerous ignore flags to the command to skip checking for some other offences. We should investigate, which of those we should still ignore, or perhaps there are opportunities for improving our chart.

Spike Time proposal

1 working day