Open jcpowermac opened 1 month ago
Hello @jcpowermac! Some important instructions when contributing to openshift/api: API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.
/test ?
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jcpowermac Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
@jcpowermac: The following commands are available to trigger required jobs:
/test build
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial
/test e2e-aws-serial-techpreview
/test e2e-upgrade
/test e2e-upgrade-minor
/test images
/test integration
/test unit
/test verify
/test verify-client-go
/test verify-crd-schema
/test verify-deps
The following commands are available to trigger optional jobs:
/test e2e-azure
/test e2e-gcp
/test okd-scos-images
Use /test all
to run the following jobs that were automatically triggered:
pull-ci-openshift-api-master-build
pull-ci-openshift-api-master-e2e-aws-ovn
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift
pull-ci-openshift-api-master-e2e-aws-ovn-techpreview
pull-ci-openshift-api-master-e2e-aws-serial
pull-ci-openshift-api-master-e2e-aws-serial-techpreview
pull-ci-openshift-api-master-e2e-azure
pull-ci-openshift-api-master-e2e-gcp
pull-ci-openshift-api-master-e2e-upgrade
pull-ci-openshift-api-master-e2e-upgrade-minor
pull-ci-openshift-api-master-images
pull-ci-openshift-api-master-integration
pull-ci-openshift-api-master-unit
pull-ci-openshift-api-master-verify
pull-ci-openshift-api-master-verify-client-go
pull-ci-openshift-api-master-verify-crd-schema
pull-ci-openshift-api-master-verify-deps
/test build /test e2e-aws-ovn
/test e2e-aws-ovn-techpreview
/test e2e-upgrade /test e2e-upgrade-minor /test images /test integration /test unit /test verify /test verify-client-go /test verify-crd-schema /test verify-deps
PR needs rebase.
@jcpowermac How many components are left that are depending on these APIs that you're aware of?
@jcpowermac How many components are left that are depending on these APIs that you're aware of?
Probably quite a few. I wanted to get an idea how difficult this would be to remove and start a discussion when we are ready.
Once the vsphere features for 4.18 are in a good place I can circle back to this effort.
I had a chat with David and we are happy to remove the API, if the tests can go green as it were, so, preferable we remove all the underlying operator code first and make this the final part
@jcpowermac: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/verify-crd-schema | 5c439451be3e132be6c24384ca708ef7a5e2d9d8 | link | true | /test verify-crd-schema |
ci/prow/integration | 5c439451be3e132be6c24384ca708ef7a5e2d9d8 | link | true | /test integration |
ci/prow/minor-e2e-upgrade-minor | 5c439451be3e132be6c24384ca708ef7a5e2d9d8 | link | true | /test minor-e2e-upgrade-minor |
ci/prow/minor-images | 5c439451be3e132be6c24384ca708ef7a5e2d9d8 | link | true | /test minor-images |
Full PR test history. Your PR dashboard.
Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with
/test all