Update disallow-helm-tiller and disallow-latest-tag to include all container types in a pod

[dolisss]

Related Issue(s)

Partially addresses #951

Description

Updating disallow-helm-tiller and disallow-latest-tag policies to handle all pod types and test cases to handle initContainers.

Checklist

• I have read the policy contribution guidelines.
• I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
• I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

[chipzoller]

Tiller (Helm v2) is so old technology I don't think it's worth making this change. Would suggest focusing on more useful policies in the present.

[dolisss]

I am updating all the best practice policies. Can you approve this one while I add the logic in other policies too?

[chipzoller]

Go ahead and make those updates. Remove from draft mode when ready for review. Please remember to follow the contribution guide as linked in the PR template. And please also ensure to increase test coverage of the policies you update in this PR as well.

[dolisss]

@chipzoller Extended the logic to the "disallow latest tag" policy along with changes needed for the chainsaw test cases.

[chipzoller]

Missing extended tests for disallow-helm-tiller.

[dolisss]

@chipzoller thought the Helm Tiller policy was outdated and that test cases might not be necessary. However, I’ve updated them now. Please review the changes

[chipzoller]

Please fix failing tests. Also complete the PR template (checklist).

[dolisss]

@chipzoller I tried updating the digest using my Mac, but the check failed. I reverted to the old digest and I think it got verified. How can I generate the digest? I am using the following command.
It's strange that it takes the digest for the other policy I generated in the same way.

 shasum -a 256 disallow-latest-tag.yaml 
2760272e57d9988ba447f62d23bba382092d00a5e14dbf00555e4170ea90593a 

[chipzoller]

Digests are expected to be generated in Linux; you can see the digest expected in the Policy Test step and use that if you're unable to generate one on your own system.

Tests still need to be fixed here.

[dolisss]

@chipzoller Thanks! it worked with Linux. What checks are you referring to? I don't see any on my page.

[chipzoller]

Please see failing CI checks.

[dolisss]

@chipzoller Please review.