-
Notifications
You must be signed in to change notification settings - Fork 408
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
OCPNODE-2333: Implement ImagePolicy CRD #4587
base: master
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: QiWang19 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 |
/test all |
@QiWang19: This pull request references OCPNODE-2333 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. In 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. |
@mtrmac PTAL |
/retest-required |
@QiWang19: This pull request references OCPNODE-2333 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. In 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. |
@QiWang19: This pull request references OCPNODE-2333 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. In 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. |
@QiWang19: This pull request references OCPNODE-2333 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. In 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. |
pkg/controller/container-runtime-config/container_runtime_config_controller.go
Outdated
Show resolved
Hide resolved
pkg/controller/container-runtime-config/container_runtime_config_controller.go
Outdated
Show resolved
Hide resolved
@@ -89,6 +89,7 @@ func (b *Bootstrap) Run(destDir string) error { | |||
idmsRules []*apicfgv1.ImageDigestMirrorSet | |||
itmsRules []*apicfgv1.ImageTagMirrorSet | |||
clusterImagePolicies []*apicfgv1alpha1.ClusterImagePolicy | |||
imagePolicies []*apicfgv1alpha1.ImagePolicy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wking @mtrmac I’m unsure about adding this to bootstrap.
I tested it by adding a manifest to the manifest directory before manually creating the cluster, and the object only appears when I set the metadate.namespace to openshift-machine-config-operator
.
I didn’t see the object when using openshift-config
or openshift-cluster-version
(I only tried these namespaces). In the enhancement, I noticed in the enhancement we might want to use ImagePolicy for release payload verifications—could this be an issue in the future?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, yeah, I'd been hoping to eventually have an openshift-cluster-version
ImagePolicy set up by the CVO by default. I'm agnostic about whether that needs to be bootstrap-time or not, but OCPBUGS-37770 had installs failing when the production CVO wanted a policy that wasn't in place at bootstrap-time.
install/0000_10_config-operator_01_imagepolicies-CustomNoUpgrade.crd.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Qi Wang <[email protected]>
@QiWang19: The following tests failed, say
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. |
- What I did
- How to verify it
- Description for the changelog