rorfs for cacheless lacks write access to /tmp/ to generate cache

[grokspawn]

Description of the change:
when we are using extractContent, but w/o extractContent.CacheDir, ensure that we have write permissions to /tmp/ by creating an emptydir volume there.

Motivation for the change:
When there is no provided CacheDir, our recent changes to set SecurityContext{ReadOnlyFilesystem: ptr.To(true)} will not allow writing to /tmp/. However, opm will need to generate a cache and cannot be told another directory to use.

Architectural changes:

Testing remarks:
#3614 passed CI with no errors, both unit which covered ExtractContent functionality including w/o CacheDir.

This is because while the unit tests validated the shape of the resulting pods but not the pods' viability in a cluster (i.e. could the pods walk the initcontainer chain successfully and bring the GRPC service up).

ginkgo test "gRPC address catalog source" does evaluate catsrc pod viability using extractContent, but never as cacheless.

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [perdasilva]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[perdasilva]

/cherry-pick release-4.20

[openshift-cherrypick-robot]

@perdasilva: cannot checkout release-4.20: error checking out "release-4.20": exit status 1 error: pathspec 'release-4.20' did not match any file(s) known to git

Details

In response to this:

/cherry-pick release-4.20

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[perdasilva]

lol whoops