CLID-226: Add analysis of OCPSTRAT-1515 in its current state

[sherine-k]

This PR contains no code.

This PR only contains the analysis done for OCPSTRATS-1515 in the light of the conversation with the Operator Framework team.

@lmzuccarelli, @aguidirh please review.

TODO:

• Decide whether to use a Dockerfile to build the final image or to use the existing logic from v1 (add an extra layer for /configs, and white-out the old one using go-containerregistry)
• Decide what to do about cache (cc @joelanford): should we change the image's CMD to remove the --cache-dir?

[openshift-ci-robot]

@sherine-k: This pull request references CLID-226 which is a valid jira issue.

In response to this:

This PR contains no code.

This PR only contains the analysis done so far for OCPSTRATS-1515 in order to close the spike CLID-226 while we wait for further instructions from @tlwu2013

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@sherine-k: This pull request references CLID-226 which is a valid jira issue.

In response to this:

This PR contains no code.

This PR only contains the analysis done so far for OCPSTRATS-1515 in order to close the spike CLID-226 while we wait for further instructions from @tlwu2013

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sherine-k

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sherine-k]

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

[openshift-ci-robot]

@sherine-k: This pull request references CLID-226 which is a valid jira issue.

In response to this:

This PR contains no code.

This PR only contains the analysis done so far for OCPSTRATS-1515 in order to close the spike CLID-226 while we wait for further instructions from @tlwu2013

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@sherine-k: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[openshift-ci-robot]

@sherine-k: This pull request references CLID-226 which is a valid jira issue.

In response to this:

This PR contains no code.

This PR only contains the analysis done for OCPSTRATS-1515 in the light of the conversation with the Operator Framework team.

@lmzuccarelli, @aguidirh please review.

TODO:

• Decide whether to use a Dockerfile to build the final image or to use the existing logic from v1 (add an extra layer for /configs, and white-out the old one using go-containerregistry)
• Decide what to do about cache (cc @joelanford): should we change the image's CMD to remove the --cache-dir?

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 openshift-eng/jira-lifecycle-plugin repository.