MCO-1522: Adapt MCO to use PIS V1 API#4934
MCO-1522: Adapt MCO to use PIS V1 API#4934openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Conversation
|
@RishabhSaini: This pull request references MCO-1522 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 story to target the "4.19.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@RishabhSaini: This pull request references MCO-1522 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 story to target the "4.19.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test unit |
|
Realized that a lot of caches where a miss since strings.TrimSpace was needed |
|
/retest-required |
Is comment out of date? It looks like openshift/client-go#314 merged and this appears to be pointing to the corresponding commit (f0faeb0f2f2e3b944101467a5eda96bc4fffe1e9)? If so, lgtm but I'd defer final approval to others on the team. |
|
@RishabhSaini: This pull request references MCO-1522 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 story to target the "4.19.0" version, but no target version was set. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
You are right, I have updated the comment to reflect this |
go.mod: Update the API and client-go pinned_image_set: use the v1 instead of v1alpha1 PIS Bump API and Client Go to latest
|
Fixed the typo mentioned here: #4948 (comment) |
|
/test bootstrap-unit |
|
@RishabhSaini: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
djoshy
left a comment
There was a problem hiding this comment.
Looks good to me, with 1 non blocking question.
And sort of a minor nit, breaking out the vendor and the remaining changes into separate commits makes reviewing and looking at history a bit easier, but again this is also non blocking 😄
/lgtm
| return ctx.Err() | ||
| default: | ||
| image := imageRef.Name | ||
| image := strings.TrimSpace(string(imageRef.Name)) |
There was a problem hiding this comment.
Could you clarify why this change was necessary? Some sort of new API validation?
There was a problem hiding this comment.
+1 Same, I'd like to know why we need this now. I see that the trimming is performed to the UID field too, that, iiuc, it's generated by k8s and cannot have whitespaces.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: djoshy, RishabhSaini The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f46921d
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: ose-machine-config-operator |
Bumps the API version
Bumps the client-go version
Modify the MCC, MCD and Tests to include the V1 PIS API