-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OWNERS: Add component Cluster Version Operator #344
Conversation
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, sdodson 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:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
What is this about? I don't see anything about |
/retest Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
It's used downstream to facilitate mapping to BZ Components. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/override ci/prow/integration |
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/integration In response to this:
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. |
Example of OpenShift components: $ curl -sH Accept:application/json -H Content-Type:application/json --data '{"jsonrpc":"2.0","method":"SelectizeJS.list_components","id":1,"params":[{"term":"..","descrs":1,"disabled":0,"product":"v314_product"}]}' https://bugzilla.redhat.com/jsonrpc.cgi | jq -r '[.result[].value] | sort[]' Build Cincinnati Cloud Compute Cloud Credential Operator Cluster Loader Cluster Version Operator Compliance Operator ... Based on Scott's [1]: > It's used downstream to facilitate mapping to BZ Components. [1]: openshift#344 (comment)
Example of OpenShift components: $ curl -sH Accept:application/json -H Content-Type:application/json --data '{"jsonrpc":"2.0","method":"SelectizeJS.list_components","id":1,"params":[{"term":"..","descrs":1,"disabled":0,"product":"v314_product"}]}' https://bugzilla.redhat.com/jsonrpc.cgi | jq -r '[.result[].value] | sort[]' Build Cincinnati Cloud Compute Cloud Credential Operator Cluster Loader Cluster Version Operator Compliance Operator ... Based on Scott's [1]: > It's used downstream to facilitate mapping to BZ Components. [1]: openshift/cluster-version-operator#344 (comment)
Based on Scott's [1]: > It's used downstream to facilitate mapping to BZ Components. I'm not sure if this property matters to us, because we are a separate Red Hat product, not a component under the OpenShift Container Project product. But 'Cincinnati Operator' no longer exists anywhere, so pointing folks at our current product name isn't breaking it any worse. [1]: openshift/cluster-version-operator#344 (comment)
Based on Scott's [1]: > It's used downstream to facilitate mapping to BZ Components. I'm not sure if this property matters to us, because we are a separate Red Hat product, not a component under the OpenShift Container Project product. But 'Cincinnati Operator' no longer exists anywhere, so pointing folks at our current product name isn't breaking it any worse. $ curl -s 'https://bugzilla.redhat.com/rest/product/OpenShift%20Update%20Service' | jq -r '.products[].name' OpenShift Update Service $ curl 'https://bugzilla.redhat.com/rest/product/Cincinnati%20Operator' {"products":[]} [1]: openshift/cluster-version-operator#344 (comment)
/cc @wking @abhinavdahiya