@@ -180,15 +180,24 @@ On a high level, the process is as follows:
180
180
to change the image references to point to your images
181
181
182
182
### Distribution specific instructions: OpenShift
183
+ Before you start, you must have the ` KUBECONFIG ` environment variable set correctly to point to your
184
+ OpenShift cluster's configuration file, and you need to be successfully logged in using the ` oc login ` command.
185
+
183
186
For convenience, the ` Makefile ` contains a target called ` deploy-openshift-dev ` which
184
187
deploys SPO in an OpenShift cluster with the appropriate defaults (SELinux is on by default)
185
- and the appropriate settings (no cert-manager needed).
188
+ and the appropriate settings (no cert-manager needed). It should be noted that ` deploy-openshit-dev `
189
+ will not enable eBPF and app-armor capabilities (APPARMOR_ENABLED=0, BPF_ENABLED=0).
186
190
187
191
If you modify the code and need to push the images to the cluster again, use the
188
192
` push-openshift-dev ` Makefile target. Because the targets use the ` ImageStream ` feature
189
193
of OpenShift, simply pushing the new images will trigger a new rollout of the deployments
190
194
and DaemonSets.
191
195
196
+ To build the SPO image with eBPF enabled, simply use ` BPF_ENABLED=1 make image ` , which will compile the image and
197
+ make it available locally at ` localhost/security-profiles-operator:latest ` . Once built, you can deploy this pre-built
198
+ image to OpenShift by running ` make deploy-prebuilt-openshift-dev ` . Subsequently, if you need to push this locally
199
+ built image to image registry used by OpenShift, execute ` make push-prebuilt-image-openshift-dev ` .
200
+
192
201
### Tearing down your test environment
193
202
At the moment, there's no teardown target provided. At the same time, some
194
203
custom resources, notably the policies themselves use finalizers which prevent
0 commit comments