Merge pull request #38797 from rh-max/srvls-sinkbinding-improvements

SRVKE-930: Sinkbinding page improvements

Author: abrennan89

modules/serverless-sinkbinding-kn.adoc

@@ -15,16 +15,6 @@ The following procedure requires you to create YAML files.
 If you change the names of the YAML files from those used in the examples, you must ensure that you also update the corresponding CLI commands.
 ====
 
-[IMPORTANT]
-====
-Before developers can use sink binding, cluster administrators must label the namespace that will be configured for sink binding with `bindings.knative.dev/include:"true"`:
-
-[source,terminal]
-----
-$ oc label namespace <namespace> bindings.knative.dev/include=true
-----
-====
-
 .Procedure
 
 . To check that sink binding is set up correctly, create a Knative event display service, or event sink, that dumps incoming messages to its log:
@@ -64,7 +54,7 @@ spec:
           restartPolicy: Never
           containers:
             - name: single-heartbeat
-              image: quay.io/openshift-knative/knative-eventing-sources-heartbeats:latest
+              image: quay.io/openshift-knative/heartbeats:latest
               args:
                 - --period=1
               env:

modules/serverless-sinkbinding-reference.adoc

@@ -204,3 +204,12 @@ This sets the `K_CE_OVERRIDES` environment variable on the `subject`:
 ----
 { "extensions": { "extra": "this is an extra attribute", "additional": "42" } }
 ----
+
+== The include label
+
+To use a SinkBinding, you need to do assign the `bindings.knative.dev/include: "true"` label to either the resource or the namespace. If the resource definition does not include the label, a cluster administrator can attach it to the namespace by running:
+
+[source,terminal]
+----
+$ oc label namespace <namespace> bindings.knative.dev/include=true
+----

modules/serverless-sinkbinding-yaml.adoc

@@ -18,16 +18,6 @@ The following procedure requires you to create YAML files.
 If you change the names of the YAML files from those used in the examples, you must ensure that you also update the corresponding CLI commands.
 ====
 
-[IMPORTANT]
-====
-Before developers can use a SinkBinding, cluster administrators must label the namespace that will be configured in the SinkBinding with `bindings.knative.dev/include:"true"`:
-
-[source,terminal]
-----
-$ oc label namespace <namespace> bindings.knative.dev/include=true
-----
-====
-
 .Procedure
 
 . To check that sink binding is set up correctly, create a Knative event display service, or event sink, that dumps incoming messages to its log.
@@ -108,7 +98,7 @@ spec:
           restartPolicy: Never
           containers:
             - name: single-heartbeat
-              image: quay.io/openshift-knative/knative-eventing-sources-heartbeats:latest
+              image: quay.io/openshift-knative/heartbeats:latest
               args:
                 - --period=1
               env: