Skip to content
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

NO-ISSUE: Update asset.yaml source for the route crd #3449

Merged

Conversation

copejon
Copy link
Contributor

@copejon copejon commented Jun 6, 2024

The route API CRD was previously source from the route-controller-manager. This has proven to be problematic since the source file path has change in the last release. MicroShift should source the CRD from the router repository instead, which should be safer in the future.

The source path used here is amd64. It doesn't matter which arch is manifest is pulled from since the CRD is not arch-dependent.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 6, 2024
@openshift-ci-robot
Copy link

@copejon: This pull request explicitly references no jira issue.

In response to this:

The route API CRD was previously source from the route-controller-manager. This has proven to be problematic since the source file path has change in the last release. MicroShift should source the CRD from the router repository instead, which should be safer in the future.

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 openshift-ci bot requested review from jerpeter1 and pmtk June 6, 2024 19:45
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 6, 2024
@copejon copejon force-pushed the no-issue-change-route-crd-src branch from 0fe0d8e to a7e8867 Compare June 6, 2024 20:15
@copejon
Copy link
Contributor Author

copejon commented Jun 6, 2024

/cherry-pick release-4.16

@openshift-cherrypick-robot

@copejon: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16

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.

@jerpeter1
Copy link
Member

Are we sure the CRD in the router repo is the one we want? The PR where route/v1/route.crd.yaml was introduced claims that it superseded https://github.com/openshift/router/blob/master/deploy/route_crd.yaml . It also looks substantially different than e.g. https://github.com/openshift/api/blob/master/route/v1/zz_generated.crd-manifests/routes-Default.crd.yaml .

… which should provide a more stable path

added cluster-config-api to embedded components so that the rebase script includes openshift/api during the git clone staging
@copejon copejon force-pushed the no-issue-change-route-crd-src branch from a7e8867 to 7285d10 Compare June 7, 2024 19:12
@copejon
Copy link
Contributor Author

copejon commented Jun 7, 2024

@jerpeter1 I've updated the PR per your recommendation. The rebase script will clone the openshift/api repository and copy the routes-Default.crd.yaml file.

Copy link
Contributor

openshift-ci bot commented Jun 7, 2024

@copejon: 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.

@ggiguash
Copy link
Contributor

ggiguash commented Jun 9, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 9, 2024
Copy link
Contributor

openshift-ci bot commented Jun 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 50457cc into openshift:main Jun 9, 2024
7 checks passed
@openshift-cherrypick-robot

@copejon: new pull request created: #3456

In response to this:

/cherry-pick release-4.16

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants