solve conflicts

Author: odacremolbap

README.md

@@ -30,6 +30,26 @@ Development version can be installed using [ko](https://github.com/ko-build/ko)
 ko apply -f ./config
 ```
 
+### Namespaced installation
+
+TriggerMesh Core controller can be configured to work with a single namespace set at the `WORKING_NAMESPACE` environment variable, which can be added editing the deployment manifest.
+
+```yaml
+        - name: WORKING_NAMESPACE
+          value: my-namespace
+```
+
+When working with a single namespace, all `ClusterRoleBindings` should also be modified adding the namespace to limit the scope of the granted permissions.
+
+```yaml
+apiVersion: rbac.authorization.k8s.io/v1
+kind: ClusterRoleBinding
+metadata:
+  name: triggermesh-core-controller
+  namespace: working
+...
+```
+
 ## Concepts
 
 TriggerMesh core contains Kubernetes objects for Brokers and Triggers:

cmd/core-controller/main.go

@@ -4,7 +4,11 @@
 package main
 
 import (
+	"os"
+
+	injection "knative.dev/pkg/injection"
 	"knative.dev/pkg/injection/sharedmain"
+	"knative.dev/pkg/signals"
 
 	"github.com/triggermesh/triggermesh-core/pkg/reconciler/memorybroker"
 	"github.com/triggermesh/triggermesh-core/pkg/reconciler/redisbroker"
@@ -13,7 +17,18 @@ import (
 )
 
 func main() {
-	sharedmain.Main("core-controller",
+
+	ctx := signals.NewContext()
+
+	// There is only one configuration item for the TriggerMesh Core controller.
+	// Instead of creating a structure and a formal configuration retrieval
+	// from environment, we use this very simplistic approach
+	ns := os.Getenv("WORKING_NAMESPACE")
+	if len(ns) != 0 {
+		ctx = injection.WithNamespaceScope(ctx, ns)
+	}
+
+	sharedmain.MainWithContext(ctx, "core-controller",
 		memorybroker.NewController,
 		redisbroker.NewController,
 		trigger.NewController,

docs/redis-broker.md

@@ -40,7 +40,7 @@ spec:
         tlsEnabled: <boolean that indicates if the Redis server is TLS protected. Optional, defaults to false>
         tlsSkipVerify: <boolean that skips verifying TLS certificates. Optional, defaults to false>
     stream: <Redis stream name. Optional, defaults to a combination of namespace and broker name>
-    streamMaxLen: <maximum number of items the Redis stream can host. Optional, defaults to unlimited>
+    streamMaxLen: <maximum number of items the Redis stream can host. Optional, defaults to 1000. Set to 0 for unlimited>
     enableTrackingID: <boolean that indicates if the Redis ID should be written as the CloudEvent attribute triggermeshbackendid>
   broker:
     port: <HTTP port for ingesting events>
@@ -52,7 +52,7 @@ The `RedisBroker` specific parameters are:
 
 - `spec.redis.connection`. When not used the broker will spin up a managed Redis Deployment. However for production scenarios that require HA and hardened security it is recommended to provide the connection to a user managed Redis instance.
 - `spec.stream` is the Redis stream name to be used by the broker. If it doesn't exists the Broker will create it.
-- `spec.streamMaxLen` is the maximum number of elements that the stream will contain.
+- `spec.streamMaxLen` is the maximum number of elements that the stream might contain. Set to 0 for unlimited.
 - `spec.enableTrackingID` when set adds the `triggermeshbackendid` CloudEvents attribute containing the Redis ID for the message to all outgoing events.
 
 The `spec.broker` section contains generic Borker parameters: