Resolve "Kyverno Policies blocks elasticsearch autoRollingUpgrade Job"

General MR

Summary

This MR resolves Kyverno compliance issues with the upgrade Job that was deployed whenever autoRollingUpgrade.enabled was set to true.

The upgrade Job itself is still having issues unrelated to the Kyverno policies that will be addressed in another MR.

Relevant logs/screenshots

To reproduce the test scenario:

1. Deploy bigbang with these values:

   elasticsearchKibana:
     enabled: true
     values:
       autoRollingUpgrade:
         enabled: true

2. Wait for bigbang deployment to complete
3. Upgrade bigbang with these values:

   elasticsearchKibana:
     enabled: true
     git:
       branch: 209-upgrade-job-kyverno-compliance
       tag: null
     values:
       autoRollingUpgrade:
         enabled: true

4. Watch for the upgrade job to start and complete successfully:

   ❯ kubectl get job -n logging
   NAME                    STATUS     COMPLETIONS   DURATION   AGE
   bb-logging-ek-upgrade   Complete   1/1           57s        115s

Linked Issue

#209 (closed)

Upgrade Notices

N/A

Closes #209 (closed)

added elasticsearch statusreview teamObservability labels

requested review from @kliu, @kscheunemann, @blairbowden, @steven.donald, and @piotr.machaj

assigned to @zcallahan

changed the description

approved this merge request

added 6 commits

• 9b82e67c...4c30c0fd - 4 commits from branch main
• a694a0e7 - fix: add `securityContext` to upgrade-job template
• 3e730079 - chore: update changelog

Compare with previous version

reset approvals from @kliu by pushing to the branch

approved this merge request

merged

mentioned in commit 36eb4351

mentioned in merge request big-bang/bigbang!5158 (merged)