Move namespace.yaml to avoid unintended deletion of other components

DEVELOPMENT.md

@@ -363,7 +363,7 @@ The `ko` command is the preferred method to manage (i.e., create, modify or dele
 You can stand up a version of Tekton using your local clone's code to the currently configured K8s context (i.e.,  `kubectl config current-context`):
 
 ```shell
-ko apply -f config/
+ko apply -R -f config/
 ```
 
 #### Verify installation
@@ -379,9 +379,15 @@ kubectl get pods -n tekton-pipelines
 You can clean up everything with:
 
 ```shell
+# If you should not delete the namespace of a pipeline component
 ko delete -f config/
+
+# If you also can delete the namespace of a pipeline component
+ko delete -R -f config/
 ```
 
+**Note:** If you use a pipeline component in the same namespace as other components such as dashboard or triggers, executing `ko delete -R -f config/` deletes these other components too.
+
 #### Redeploy controller
 
 As you make changes to the code, you can redeploy your controller with:
@@ -403,9 +409,9 @@ set -e
 # Set your target namespace here
 TARGET_NAMESPACE=new-target-namespace
 
-ko resolve -f config | sed -e '/kind: Namespace/!b;n;n;s/:.*/: '"${TARGET_NAMESPACE}"'/' | \
+ko resolve -R -f config | sed -e '/kind: Namespace/!b;n;n;s/:.*/: '"${TARGET_NAMESPACE}"'/' | \
     sed "s/namespace: tekton-pipelines$/namespace: ${TARGET_NAMESPACE}/" | \
-    kubectl apply -f-
+    kubectl apply -R -f-
 kubectl set env deployments --all SYSTEM_NAMESPACE=${TARGET_NAMESPACE} -n ${TARGET_NAMESPACE}
 ```
 

Makefile

@@ -65,12 +65,12 @@ KO = $(or ${KO_BIN},${KO_BIN},$(BIN)/ko)
 $(BIN)/ko: PACKAGE=github.com/google/ko
 
 .PHONY: apply
-apply: | $(KO) ; $(info $(M) ko apply -f config/) @ ## Apply config to the current cluster
-	$Q $(KO) apply -f config
+apply: | $(KO) ; $(info $(M) ko apply -R -f config/) @ ## Apply config to the current cluster
+	$Q $(KO) apply -R -f config
 
 .PHONY: resolve
-resolve: | $(KO) ; $(info $(M) ko resolve -f config/) @ ## Resolve config to the current cluster
-	$Q $(KO) resolve --push=false --oci-layout-path=$(BIN)/oci -f config
+resolve: | $(KO) ; $(info $(M) ko resolve -R -f config/) @ ## Resolve config to the current cluster
+	$Q $(KO) resolve --push=false --oci-layout-path=$(BIN)/oci -R -f config
 
 .PHONY: generated
 generated: | vendor ; $(info $(M) update generated files) ## Update generated files

tekton/publish.yaml

@@ -157,11 +157,11 @@ spec:
       # Publish images and create release.yaml
       mkdir -p $OUTPUT_RELEASE_DIR
 
-      ko resolve --platform=$(params.platforms) --preserve-import-paths -t $(params.versionTag) -f ${PROJECT_ROOT}/config/ > $OUTPUT_RELEASE_DIR/release.yaml
+      ko resolve --platform=$(params.platforms) --preserve-import-paths -t $(params.versionTag) -R -f ${PROJECT_ROOT}/config/ > $OUTPUT_RELEASE_DIR/release.yaml
       # Publish images and create release.notags.yaml
       # This is useful if your container runtime doesn't support the `image-reference:tag@digest` notation
       # This is currently the case for `cri-o` (and most likely others)
-      ko resolve --platform=$(params.platforms) --preserve-import-paths -f ${PROJECT_ROOT}/config/ > $OUTPUT_RELEASE_DIR/release.notags.yaml
+      ko resolve --platform=$(params.platforms) --preserve-import-paths -R -f ${PROJECT_ROOT}/config/ > $OUTPUT_RELEASE_DIR/release.notags.yaml
 
   - name: koparse
     image: gcr.io/tekton-releases/dogfooding/koparse:latest

test/README.md

@@ -4,7 +4,7 @@ To run tests:
 
 ```shell
 # Land the latest codes
-ko apply -f ./config/
+ko apply -R -f ./config/
 
 # Unit tests
 go test ./...

test/e2e-common.sh

@@ -20,11 +20,11 @@ source $(git rev-parse --show-toplevel)/vendor/github.com/tektoncd/plumbing/scri
 
 function install_pipeline_crd() {
   echo ">> Deploying Tekton Pipelines"
-  ko resolve -f config/ \
+  ko resolve -R -f config/ \
       | sed -e 's%"level": "info"%"level": "debug"%' \
       | sed -e 's%loglevel.controller: "info"%loglevel.controller: "debug"%' \
       | sed -e 's%loglevel.webhook: "info"%loglevel.webhook: "debug"%' \
-      | kubectl apply -f - || fail_test "Build pipeline installation failed"
+      | kubectl apply -R -f - || fail_test "Build pipeline installation failed"
   verify_pipeline_installation
 
   export SYSTEM_NAMESPACE=tekton-pipelines
@@ -47,7 +47,7 @@ function verify_pipeline_installation() {
 
 function uninstall_pipeline_crd() {
   echo ">> Uninstalling Tekton Pipelines"
-  ko delete --ignore-not-found=true -f config/
+  ko delete --ignore-not-found=true -R -f config/
 
   # Make sure that everything is cleaned up in the current namespace.
   delete_pipeline_resources

test/presubmit-tests.sh

@@ -59,7 +59,7 @@ function check_yaml_lint() {
 
 function ko_resolve() {
   header "Running `ko resolve`"
-  KO_DOCKER_REPO=example.com ko resolve --platform=all --push=false -f config 1>/dev/null
+  KO_DOCKER_REPO=example.com ko resolve --platform=all --push=false -R -f config 1>/dev/null
 }
 
 function post_build_tests() {