Skip to content

Conversation

@Prashanth684
Copy link
Contributor

@Prashanth684 Prashanth684 commented Aug 16, 2024

As per openshift/enhancements#1605, there was a
new field introduced in the image config spec and status which reflects
the global value to be set for imagestream import mode which is behind a
featuregate. This PR reads the observed config, checks if the importmode
string is present and uses it as the default when creating imagestreams.

API changes: openshift/api#1928
cluster-openshift-apiserver-operator changes: openshift/cluster-openshift-apiserver-operator#582
image-registry-operator changes: openshift/cluster-image-registry-operator#109

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

openshift-ci-robot commented Aug 16, 2024

@Prashanth684: This pull request references MULTIARCH-4558 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.18.0" version, but no target version was set.

Details

In response to this:

As per openshift/enhancements#1605, there was a
new field introduced in the image config spec and status which reflects
the global value to be set for imagestream import mode which is behind a
featuregate. This PR reads the observed config, checks if the importmode
string is present and uses it as the default when creating imagestreams.

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-robot
Copy link

openshift-ci-robot commented Aug 20, 2024

@Prashanth684: This pull request references MULTIARCH-4558 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.18.0" version, but no target version was set.

Details

In response to this:

As per openshift/enhancements#1605, there was a
new field introduced in the image config spec and status which reflects
the global value to be set for imagestream import mode which is behind a
featuregate. This PR reads the observed config, checks if the importmode
string is present and uses it as the default when creating imagestreams.

API changes: openshift/api#1928
cluster-openshift-apiserver-operator changes: openshift/cluster-openshift-apiserver-operator#582
image-registry-operator changes: openshift/cluster-image-registry-operator#109

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
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good.
The verify job will fail due to some changes on code-generator that breaks some scripts. I'm working on resolving that issue.

Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall, looks good.
Can you squash the all changes on go.mod and vendor into 1 commit and let the plugin code change in a separate commit?
The verify test will continue to fail until we fix the code-gen changes on the scripts. However, other tests should pass.

@Prashanth684 Prashanth684 force-pushed the importmode-apiserver branch 2 times, most recently from 99b7cc7 to 482c932 Compare September 10, 2024 22:11
@Prashanth684
Copy link
Contributor Author

waiting for #441.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 30, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 8, 2024
@Prashanth684
Copy link
Contributor Author

@dinhxuanvu @tkashem rebased after #441 and bumped api version. Should be good now.

…ed config changes in the image config

As per openshift/enhancements#1605, there was a
new field introduced in the image config spec and status which reflects
the global value to be set for imagestream import mode which is behind a
featuregate. This PR reads the observed config, checks if the importmode
string is present and uses it as the default when creating imagestreams.
Copy link
Member

@dinhxuanvu dinhxuanvu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2024
@dinhxuanvu
Copy link
Member

@tkashem For the final review/approval.

@tkashem
Copy link
Contributor

tkashem commented Nov 22, 2024

usually defaults are hardcoded values, but this one is more dynamic, and so needs this convoluted way, approving based on David's suggestion here: https://redhat-internal.slack.com/archives/C013VBYBJQH/p1711628286172049?thread_ts=1711476458.959689&cid=C013VBYBJQH

Maybe an admission plugin can help here (or CEL when mutating policy is available maybe?), something worth looking into before we promote it from TechPreview

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dinhxuanvu, Prashanth684, tkashem

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

The pull request process is described here

Details 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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 22, 2024
@Prashanth684 Prashanth684 added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Nov 22, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 22, 2024

@Prashanth684: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 4616af6 into master Nov 22, 2024
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-openshift-apiserver
This PR has been included in build ose-openshift-apiserver-container-v4.18.0-202411222306.p0.g4616af6.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. 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.

6 participants