Skip to content

OCPNODE-2552: Add ImagePolicy to the list of valid config manifests#5094

Closed
QiWang19 wants to merge 1 commit into
openshift:mainfrom
QiWang19:imagepolicy
Closed

OCPNODE-2552: Add ImagePolicy to the list of valid config manifests#5094
QiWang19 wants to merge 1 commit into
openshift:mainfrom
QiWang19:imagepolicy

Conversation

@QiWang19

@QiWang19 QiWang19 commented Nov 8, 2024

Copy link
Copy Markdown
Member

What this PR does / why we need it:
Add ImagePolicy CRD to valid manifests as MCO bootstraps it. This is a namespaced CRD for image sigstore signature verification. Previously, we introduced the ClusterImagePolicy in PR #3894 to support IBM ROKS deployments.
This change aligns with our ongoing effort to ensure Hypershift remains consistent with OpenShift's functionality.
we also allow hypershift users to configure imagepolicy for their namespaces, make sure hypershift provides the same set of features as OpenShift.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com//browse/OCPNODE-2552

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

@QiWang19 QiWang19 changed the title Add ImagePolicy to the list of valid config manifests OCPNODE-2552: Add ImagePolicy to the list of valid config manifests Nov 8, 2024
@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 8, 2024
@openshift-ci-robot

openshift-ci-robot commented Nov 8, 2024

Copy link
Copy Markdown

@QiWang19: This pull request references OCPNODE-2552 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:

What this PR does / why we need it:
Add ImagePolicy CRD to valid manifests as MCO bootstraps it
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit 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.

@openshift-ci openshift-ci Bot added area/api Indicates the PR includes changes for the API area/cli Indicates the PR includes changes for CLI area/documentation Indicates the PR includes changes for documentation area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release and removed do-not-merge/needs-area labels Nov 8, 2024
@netlify

netlify Bot commented Nov 8, 2024

Copy link
Copy Markdown

Deploy Preview for hypershift-docs ready!

Name Link
🔨 Latest commit e2eb80c
🔍 Latest deploy log https://app.netlify.com/sites/hypershift-docs/deploys/673bb9a210349a00088f2ca1
😎 Deploy Preview https://deploy-preview-5094--hypershift-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@openshift-ci-robot

openshift-ci-robot commented Nov 8, 2024

Copy link
Copy Markdown

@QiWang19: This pull request references OCPNODE-2552 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:

What this PR does / why we need it:
Add ImagePolicy CRD to valid manifests as MCO bootstraps it. This is a namespaced CRD for image sigstore signature verification.
We have added ClusterImagePoily before in PR #3894
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit 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.

@bryan-cox

Copy link
Copy Markdown
Member

/retest

@bryan-cox

Copy link
Copy Markdown
Member

Can you add the "why" in the commit description please? - See 5. in https://hypershift-docs.netlify.app/contribute/#prior-to-submitting-a-pull-request.

@jparrill

Copy link
Copy Markdown
Contributor

Hey @QiWang19 thanks for the PR, could you please take a look to the Bryan's comment?

@openshift-ci-robot

openshift-ci-robot commented Nov 18, 2024

Copy link
Copy Markdown

@QiWang19: This pull request references OCPNODE-2552 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:

What this PR does / why we need it:
Add ImagePolicy CRD to valid manifests as MCO bootstraps it. This is a namespaced CRD for image sigstore signature verification. Previously, we introduced the ClusterImagePolicy in PR #3894 to support IBM ROKS deployments.
This change aligns with our ongoing effort to ensure Hypershift remains consistent with OpenShift's functionality.
we also allow hypershift users to configure imagepolicy for their namespaces, make sure hypershift provides the same set of features as OpenShift.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit 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.

@openshift-ci-robot

openshift-ci-robot commented Nov 18, 2024

Copy link
Copy Markdown

@QiWang19: This pull request references OCPNODE-2552 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:

What this PR does / why we need it:
Add ImagePolicy CRD to valid manifests as MCO bootstraps it. This is a namespaced CRD for image sigstore signature verification. Previously, we introduced the ClusterImagePolicy in PR #3894 to support IBM ROKS deployments.
This change aligns with our ongoing effort to ensure Hypershift remains consistent with OpenShift's functionality.
we also allow hypershift users to configure imagepolicy for their namespaces, make sure hypershift provides the same set of features as OpenShift.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com//browse/OCPNODE-2552

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit 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.

@QiWang19

Copy link
Copy Markdown
Member Author

/retest

@QiWang19

Copy link
Copy Markdown
Member Author

I updated the commit. PTAL @bryan-cox @jparrill

@jparrill

Copy link
Copy Markdown
Contributor

/retest

@jparrill jparrill left a comment

Copy link
Copy Markdown
Contributor

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 19, 2024
@jparrill

Copy link
Copy Markdown
Contributor

/lgtm cancel

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 19, 2024
@jparrill

Copy link
Copy Markdown
Contributor

@QiWang19 could you update the commit message with the OCPNODE id you have in the title and add some details you have in this PR's first message too as additional text?. Thanks!

Let me know for tagging.

Add ImagePolicy CRD to valid manifests as MCO bootstraps it. This is a namespaced CRD for image sigstore signature verification. Previously, we introduced the ClusterImagePolicy in PR openshift#3894 to support IBM ROKS deployments.
This change aligns with our ongoing effort to ensure Hypershift remains consistent with OpenShift's functionality.
we also allow hypershift users to configure imagepolicy for their namespaces, make sure hypershift provides the same set of features as OpenShift.

Signed-off-by: Qi Wang <qiwan@redhat.com>
@QiWang19

Copy link
Copy Markdown
Member Author

@jparrill commit updated. PTAL

@openshift-ci

openshift-ci Bot commented Nov 19, 2024

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: QiWang19
Once this PR has been reviewed and has the lgtm label, please ask for approval from jparrill. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@enxebre

enxebre commented Nov 19, 2024

Copy link
Copy Markdown
Member

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 19, 2024
@openshift-ci

openshift-ci Bot commented Nov 19, 2024

Copy link
Copy Markdown
Contributor

@QiWang19: 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-aks ba581cd link true /test e2e-aks
ci/prow/e2e-kubevirt-aws-ovn-reduced ba581cd link true /test e2e-kubevirt-aws-ovn-reduced
ci/prow/e2e-aws ba581cd link true /test e2e-aws
ci/prow/images ba581cd link true /test images

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.

@enxebre

enxebre commented Nov 27, 2024

Copy link
Copy Markdown
Member

Since ImageTagMirrorSet is cluster wide resource we'll come up with a semantic to expose it in the HC.

@QiWang19 QiWang19 closed this Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/api Indicates the PR includes changes for the API area/cli Indicates the PR includes changes for CLI area/documentation Indicates the PR includes changes for documentation area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants