Skip to content

Conversation

yuqi-zhang
Copy link
Contributor

This adds switching to v1 CRDs in the payload manifests directly, on top of the changes in #2090. This should work in theory since no tests are currently dependent on this, and the MCO doesn't directly use any of these objects unless both the featuregate is turned on, and the user directly opts a pool into layered builds, which at this time should only be MCO-internal tech preview tests.

First step to GA'ing the currently v1alpha1 APIs. Don't add to payload
manifests yet, and the featuregate is retained.
Mostly fixups, with some minor changes to the v1alpha1 API:

 - Removed Version and ConfigGeneration from MOSB as they were unused
 - Updated relatedobjects list
 - Changed all optional,omitempty structs to pointers
 - Removed default for ImageBuilderType, but keeping default build arch
   to noarch as we don’t foresee changing that.
 - Fixed RenderedImagePushspec validators to match description
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 15, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 15, 2024

@yuqi-zhang: This pull request references MCO-1443 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.0" version, but no target version was set.

In response to this:

This adds switching to v1 CRDs in the payload manifests directly, on top of the changes in #2090. This should work in theory since no tests are currently dependent on this, and the MCO doesn't directly use any of these objects unless both the featuregate is turned on, and the user directly opts a pool into layered builds, which at this time should only be MCO-internal tech preview tests.

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.

Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

Hello @yuqi-zhang! 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.

@openshift-ci openshift-ci bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Nov 15, 2024
Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuqi-zhang
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

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

Copy link
Contributor

openshift-ci bot commented Dec 4, 2024

@yuqi-zhang: 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/e2e-aws-ovn-hypershift a6b3eb5 link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-gcp a6b3eb5 link false /test e2e-gcp
ci/prow/e2e-aws-ovn-techpreview a6b3eb5 link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-serial-techpreview a6b3eb5 link true /test e2e-aws-serial-techpreview
ci/prow/lint a6b3eb5 link true /test lint

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.

@yuqi-zhang
Copy link
Contributor Author

/close

In favour of #2090

@openshift-ci openshift-ci bot closed this Dec 4, 2024
Copy link
Contributor

openshift-ci bot commented Dec 4, 2024

@yuqi-zhang: Closed this PR.

In response to this:

/close

In favour of #2090

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants