Updating Seldon Community Operator from 2.8 to 3.1

[axsaucedo]

This pull request contains the changes required to update the Seldon Community Operator from 2.8 to 3.1 (CSV versions 0.1.2 to 0.1.3).

[openshift-ci-robot]

Hi @axsaucedo. Thanks for your PR.

I'm waiting for a operator-framework or openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[tmckayus]

@aneeshkp ptal

[tmckayus]

Note that the deployment name for the seldon controller was changed to get around the issue reported in operator-framework/operator-lifecycle-manager#952 (the selector/labels for the controller deployment changed)

[tmckayus]

Looks like sedonoperator.crd.yaml needs the status subresource added, this is apparently why the scorecard is failing (there is no status block!)

seldonoperator-crd-yaml.txt
@axsaucedo

[axsaucedo]

Thank you @tmckayus - this has been updated with the latest CSV.

[aneeshkp]

/test CVP

[aneeshkp]

/ok-to-test

[aneeshkp]

/retest