From 64f5b0bd7842a26d0afc194b0025696eaad46230 Mon Sep 17 00:00:00 2001 From: Vibhu Prashar Date: Thu, 2 Nov 2023 00:43:40 +0530 Subject: [PATCH] docs: Update FAQ for community operator Signed-off-by: Vibhu Prashar --- docs/installation/community-operator.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/installation/community-operator.md b/docs/installation/community-operator.md index 5225b460..af83a4d3 100644 --- a/docs/installation/community-operator.md +++ b/docs/installation/community-operator.md @@ -235,3 +235,19 @@ Once Kepler Instance is created all the related resources like pods, daemonsets, ```sh oc get all -n openshift-kepler-operator ``` + +### How do I enable libbpf images? + +**NOTE:** This annotation will only exist until Kepler `0.7` is released which will default to `libbpf` and discontinue `bcc` + +You can specify **annotations** for Kepler at the time of creating the Instance. + +To specify in `YAML` view: + +```yaml +metadata: + annotations: + kepler.sustainable.computing.io/bpf-attach-method: bcc/libbpf +``` + +Here `bcc` requires OCP 4.13 and above whereas `libbpf` can work with OCP 4.13 or below.