CIS_INVALID_VALUE_SECCOMP_PROFILE Is reporting error when it should not

[Socolin]

Since today I'm getting errors on validation about CIS_INVALID_VALUE_SECCOMP_PROFILE on resource kind that seems very weird:

• Service
• Ingress
• AzureIdentityBinding
• HorizontalPodAutoscaler

I'm not sure I understand why it's required on those ?

[noorul]

Team, this is a blocker. I don't see a workaround also. It is surprising to see breaking behaviour without even a version change.

[noorul]

It is failing for this sample manifest

apiVersion: autoscaling.k8s.io/v1
kind: VerticalPodAutoscaler
metadata:
  name: sample-vpa
  namespace: gravity
spec:
  resourcePolicy:
    containerPolicies:
    - containerName: '*'
      controlledResources:
      - cpu
      - memory
  targetRef:
    apiVersion: apps/v1
    kind: StatefulSet
    name: sample
  updatePolicy:
    updateMode: Auto

[hadar-co]

@Socolin @noorul an incorrect fix was committed which caused these issues, will be fixed shortly:)

[noorul]

@hadar-co But this kind of mistake impacts everyone. May be policy changes should be gated properly. We have hundreds of repositories dependent on this. Our CI builds are failing and changes to those repositories are blocked.