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 installed SOP via Helm. helm install security-profiles-operator --namespace security-profiles-operator https://github.com/kubernetes-sigs/security-profiles-operator/releases/download/v0.8.4/security-profiles-operator-0.8.4.tgz
What you expected to happen:
LOCALHOSTPROFILE should be populated so it can be referenced by pods as the LocalhostProfile field.
How to reproduce it (as minimally and precisely as possible):
Just install SOP 0.8.4, create a seccompprofile resource in the SAME namespace. It should create but never reach any status of 'Installed' and LOCALHOSTPROFILE is empty.
Anything else we need to know?:
I have tried creating in default namespace and the security-profiles-operator where i installed SOP. Both do not work.
Two of the 3 pods seem to have this log:
Environment:
Cloud provider or hardware configuration: GKE
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:
The text was updated successfully, but these errors were encountered:
What happened:
I installed SOP via Helm.
helm install security-profiles-operator --namespace security-profiles-operator https://github.com/kubernetes-sigs/security-profiles-operator/releases/download/v0.8.4/security-profiles-operator-0.8.4.tgz
What you expected to happen:
LOCALHOSTPROFILE should be populated so it can be referenced by pods as the LocalhostProfile field.
How to reproduce it (as minimally and precisely as possible):
Just install SOP 0.8.4, create a seccompprofile resource in the SAME namespace. It should create but never reach any status of 'Installed' and LOCALHOSTPROFILE is empty.
Anything else we need to know?:
I have tried creating in default namespace and the security-profiles-operator where i installed SOP. Both do not work.
Two of the 3 pods seem to have this log:
Environment:
cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: