You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using AKS for the deployment. I am using version v1.5.3 On the Azure Defender, there is a recommendation to add an AppArmor profile. I thought of using the "runtime/default" profile. This will be added as an annotation. Once added "/proc" and "/sys" access will be restricted. I just want to know if these paths are being used in the cert-manager-webhook, cert-manager-cainjector and cert-manager. If not I can proceed to add the default AppArmor profile.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using AKS for the deployment. I am using version
v1.5.3
On the Azure Defender, there is a recommendation to add an AppArmor profile. I thought of using the "runtime/default" profile. This will be added as an annotation. Once added "/proc" and "/sys" access will be restricted. I just want to know if these paths are being used in the cert-manager-webhook, cert-manager-cainjector and cert-manager. If not I can proceed to add the default AppArmor profile.Beta Was this translation helpful? Give feedback.
All reactions