Skip to content
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

Receiving issue for helm deployment of wiz-kubernetes-integration to ArgoCD #405

Open
romelBen opened this issue Oct 2, 2024 · 2 comments

Comments

@romelBen
Copy link

romelBen commented Oct 2, 2024

Using wiz-kubernetes-integration-0.1.136, I am receiving this error in ArgoCD if our Kubernetes is version 1.30:

Failed to compare desired state to live state: failed to calculate diff: error calculating structured merge diff: error building typed value from live resource: .spec.template.spec.containers[name="wiz-sensor"].securityContext.appArmorProfile: field not declared in schema

I was checking to see if I can disable it in the helm charts but I'm not able. This is of course for wiz-sensor. The 2 sections of code would be the following:

daemonset.yaml

{{- if semverCompare "<1.31" $kubeVersion }}
container.apparmor.security.beta.kubernetes.io/wiz-sensor: unconfined
{{- if .Values.diskScan.enabled }}
container.apparmor.security.beta.kubernetes.io/wiz-disk-scanner: unconfined
{{- end }}
{{- end }}

{{- if semverCompare ">=1.30" $kubeVersion }}
appArmorProfile:
type: Unconfined
{{- end }}

If our nodes do not have appArmor disabled. Would this be considered an issue or is there something on our side where we need to disable appArmor?

@ariknem
Copy link
Contributor

ariknem commented Oct 3, 2024

Yea it's a bit tricky there. The feature is in beta in 1.30 but is usually open: https://kubernetes.io/docs/tutorials/security/apparmor/

we have the legacy annotation on the pod to disable apparmor:
container.apparmor.security.beta.kubernetes.io/wiz-sensor: unconfined

so I think it should be fine.

you see some of the other kubernetes variant explicitly disallow the old annotation even in 1.30.. if you don't see a system health issue for the sensor in the wiz portal it means it's all fine.

@ariknem
Copy link
Contributor

ariknem commented Nov 6, 2024

was this resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants