Replace default namespace to runtime-component for kustomize artifacts (#532)

Author: halim-lee

Makefile

@@ -93,8 +93,8 @@ endif
 # Produce CRDs that work back to Kubernetes 1.11 (no version conversion)
 CRD_OPTIONS ?= "crd:crdVersions=v1,generateEmbeddedObjectMeta=true"
 
-# Produce files under internal/deploy/kustomize/daily with default namespace
-KUSTOMIZE_NAMESPACE = default
+# Produce files under internal/deploy/kustomize/daily with runtime-component namespace
+KUSTOMIZE_NAMESPACE = runtime-component
 KUSTOMIZE_IMG = icr.io/appcafe/runtime-component-operator:daily
 
 # Use docker if available. Otherwise default to podman. 

config/kustomize/operator/kustomization.yaml

@@ -4,7 +4,7 @@ resources:
 - ../../manager
 
 # Adds namespace to all resources.
-namespace: default
+namespace: runtime-component
 namePrefix: rco-
 
 # Labels to add to all resources and selectors.

config/kustomize/roles/kustomization.yaml

@@ -4,7 +4,7 @@ resources:
 - ../../rbac
 
 # Adds namespace to all resources.
-namespace: default
+namespace: runtime-component
 namePrefix: rco-
 
 # Labels to add to all resources and selectors.

internal/deploy/kustomize/1.2.0/README.adoc

@@ -1,48 +1,47 @@
 = Installing the Runtime Component Operator using kustomize
 
-This directory contains kustomize files that can be used to install the operator
-in your cluster in various different configurations, and also some example overlays
-which show how the installation can be customized.
+This directory contains configuration files that helps installing the Runtime Component operator
+using `kustomize` with the Kubernetes command-line interface (CLI) (`kubectl`). These configurations
+are useful when the cluster is not a Red Hat® OpenShift® Container Platform cluster or when
+Operator Lifecycle Manager is not being used.
 
-== Install and watch own namespace
+== Installing and watching own namespace
 
 === base
-The simplest configuration will install the operator into the 'default' namespace, and the operator
-will watch for Runtime Component custom resource instances only in its own namespace. To install, run:
-`kubectl create -k base`
-and to uninstall, run:
-`kubectl delete -k base`
+The base configuration installs the operator into the 'runtime-component' namespace,
+and the operator watches for Runtime Component custom resource instances only in its own namespace.
+Create a namespace called 'runtime-component' for the operator.
+To install, run: `kubectl create -k base` and to uninstall, run: `kubectl delete -k base`
 
 === examples/watch-own-namespace
-This example overlay demonstrates how to modify the base configuration to install/watch a
-namespace other than 'default'. The example installs the operator to a namespace called
-'rco-ns' which should already exist. To install, run `kubectl create -k examples/watch-own-namespace`
+This example overlay demonstrates how to modify the base configuration to install the operator and have it
+watch a namespace other than 'runtime-component'. Create a namespace called 'rco-ns' for the operator.
+To install the operator into the 'rco-ns' namespace, run: `kubectl create -k examples/watch-own-namespace`
 
-== Install and watch another namespace
+== Installing and watching another namespace
 
 === overlays/watch-another-namespace
 This overlay installs the operator into the namespace 'rco-ns', but configures it to
-watch for Runtime Component custom resource instances in a different namespace called 'rco-watched-ns'. As
-this overlay install resources into two different namespaces, the namespace must not be specified
-in the kustomize.yaml file. To install, run `kubectl create -k overlays/watch-another-namespace`
+watch for Runtime Component custom resource instances in a different namespace called 'rco-watched-ns'.
+Because this overlay installs resources into two different namespaces, the namespace must not be specified
+in the kustomize.yaml file. To install, run:  `kubectl create -k overlays/watch-another-namespace`
 
 === examples/watch-another-namespace
-This example overlay builds on the previous one, but demonstrates how to change the
-install and watched namespaces. In this case, the operator is installed into 'rco-ns2'
-and it will watch for resources in 'rco-watched-ns2'. To install run `kubectl create -k
+This example overlay builds on the previous example, but demonstrates how to change
+the install and watched namespaces. In this case, the operator is installed into 'rco-ns2'
+and watches for resources in 'rco-watched-ns2'. To install run: `kubectl create -k
 examples/watch-another-namespace`
 
-== Install and watch all namespaces
+== Installing and watching all namespaces
 
 === overlays/watch-all-namespaces
-This overlay installs the operator into the default namespace, but configures it
-to watch for Runtime Component custom resource instances in any namespace. Compared to the base,
-this requires additional ClusterRoles and ClusterRoleBindings. To install run:
-`kubectl create -k overlays/watch-all-namespaces`
+This overlay installs the operator into the 'runtime-component' namespace,
+but configures it to watch for Runtime Component custom resource instances in any namespaces.
+Compared to the base configuration, this overlay requires additional ClusterRoles and ClusterRoleBindings.
+To install, run: `kubectl create -k overlays/watch-all-namespaces`
 
 === examples/watch-all-namespaces
-This example overlay builds on the previous one, and demonstrates how to change
-which namespace the operator is installed into. In this example, the operator
-is installed into a namespace called 'rco-ns', and will still watch for
-Runtime Component custom resource instances in any namespace. To install, run:
-`kubectl create -k examples/watch-all-namespaces`
+This example overlay builds on the previous example and demonstrates how to change
+the namespace that the operator installs into. In this example, the operator installs
+into a namespace that is called 'rco-ns' and watches for Runtime Component custom resource
+instances in any namespaces. To install, run: `kubectl create -k examples/watch-all-namespaces`

internal/deploy/kustomize/1.2.0/base/kustomization.yaml

@@ -1,7 +1,7 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
-namespace: default
+namespace: runtime-component
 
 resources:
   - runtime-component-crd.yaml

internal/deploy/kustomize/1.2.0/base/runtime-component-operator.yaml

@@ -6,7 +6,7 @@ metadata:
     app.kubernetes.io/name: runtime-component-operator
     control-plane: controller-manager
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component
 spec:
   replicas: 1
   selector:

internal/deploy/kustomize/1.2.0/base/runtime-component-roles.yaml

@@ -5,7 +5,7 @@ metadata:
     app.kubernetes.io/instance: runtime-component-operator
     app.kubernetes.io/name: runtime-component-operator
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
@@ -14,7 +14,7 @@ metadata:
     app.kubernetes.io/instance: runtime-component-operator
     app.kubernetes.io/name: runtime-component-operator
   name: rco-leader-election-role
-  namespace: default
+  namespace: runtime-component
 rules:
 - apiGroups:
   - ""
@@ -64,7 +64,7 @@ metadata:
     app.kubernetes.io/instance: runtime-component-operator
     app.kubernetes.io/name: runtime-component-operator
   name: rco-manager-role
-  namespace: default
+  namespace: runtime-component
 rules:
 - apiGroups:
   - apps
@@ -234,15 +234,15 @@ metadata:
     app.kubernetes.io/instance: runtime-component-operator
     app.kubernetes.io/name: runtime-component-operator
   name: rco-leader-election-rolebinding
-  namespace: default
+  namespace: runtime-component
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: Role
   name: rco-leader-election-role
 subjects:
 - kind: ServiceAccount
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
@@ -251,12 +251,12 @@ metadata:
     app.kubernetes.io/instance: runtime-component-operator
     app.kubernetes.io/name: runtime-component-operator
   name: rco-manager-rolebinding
-  namespace: default
+  namespace: runtime-component
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: Role
   name: rco-manager-role
 subjects:
 - kind: ServiceAccount
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component

internal/deploy/kustomize/1.2.0/overlays/watch-all-namespaces/cluster-roles.yaml

@@ -238,7 +238,7 @@ roleRef:
 subjects:
 - kind: ServiceAccount
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
@@ -254,5 +254,5 @@ roleRef:
 subjects:
 - kind: ServiceAccount
   name: rco-controller-manager
-  namespace: default
+  namespace: runtime-component
 ---

internal/deploy/kustomize/1.2.0/overlays/watch-all-namespaces/kustomization.yaml

@@ -1,7 +1,7 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
-namespace: default
+namespace: runtime-component
 
 bases:
 - ../../base

internal/deploy/kustomize/1.2.0/overlays/watch-all-namespaces/rco-all-namespaces.yaml

@@ -2,6 +2,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: rco-controller-manager
+  namespace: runtime-component
 spec:
   template:
     spec: