No GC Handler#27
Conversation
fdb47d0 to
61fb857
Compare
| // Noop label | ||
| if _, ok := updatedManifest.GetLabels()["imagemanifestvuln.example"]; ok { | ||
| return nil | ||
| } |
There was a problem hiding this comment.
Put this before updatedManifest is called.
| } | ||
|
|
||
| func (l *Labeller) handleNoop(obj, oldObj *secscanv1alpha1.ImageManifestVuln) { | ||
| if _, ok := obj.GetLabels()["imagemanifestvuln.example"]; ok && !reflect.DeepEqual(obj.Spec, oldObj.Spec) { |
There was a problem hiding this comment.
Should we change the label name to something more descriptive?
imagemanifestvuln.skipgc?
Also, is an annotation better for this use case?
|
|
||
| func (l *Labeller) handleNoop(obj, oldObj *secscanv1alpha1.ImageManifestVuln) { | ||
| if _, ok := obj.GetLabels()["imagemanifestvuln.example"]; ok && !reflect.DeepEqual(obj.Spec, oldObj.Spec) { | ||
| _, err := l.sclient.SecscanV1alpha1().ImageManifestVulns(obj.GetNamespace()).UpdateStatus(updateImageManifestVulnLastUpdate(obj)) |
There was a problem hiding this comment.
It's not really a noop if it's updating the status.
There was a problem hiding this comment.
Right, noop isn't the best wording. We're essentially trying to implement something that will pass the operator-scorecard test that assumes that a user will create an ImageManifestVuln from the alm-examples annotation on our CSV, and expects the status block to change if they update the spec. This Operator doesn't work like that, but we can add a special handler for it.
649685d to
f208adf
Compare
|
Holding off on merging until I confirm it passes the |
f208adf to
dba8174
Compare
|
@alecmerdler: PR needs rebase. 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/test-infra repository. |
2 participants
Description
If an
ImageManifestVulnis created by a user with the noop label, don't garbage collect it.Fixes this test issue with
operator-scorecard