Merge pull request #55040 from Dhruv-Soni11/RHDEVDOCS-4891

Added the new changes for 1.9 Pipelines RN

Author: bburt-rh

modules/op-release-notes-1-9.adoc

@@ -77,7 +77,12 @@ In addition to the fixes and stability improvements, the following sections high
 [id="operator-new-features-1-9_{context}"]
 === Operator
 
-* With this update, you can install {pac} as a separate component, not as a part of `TektonAddon`. You can configure {pac} in the `TektonConfig` CRD.
+* With this update, {pac} is installed by default. You can disable {pac} by using the `-p` flag:
++
+[source,yaml]
+----
+$ oc patch tektonconfig config --type="merge" -p '{"spec": {"platforms": {"openshift":{"pipelinesAsCode": {"enable": false}}}}}'
+----
 
 * With this update, you can also modify {pac} configurations in the `TektonConfig` CRD.
 
@@ -246,7 +251,10 @@ If you do not add any configuration data, you can use the default data in the AP
 
 * With this update, support for `tekton.dev/v1alpha1` API pipeline resources, such as Pipeline, PipelineRun, Task, Clustertask, and TaskRun has been removed.	
 
-* With this update, the `tkn-pac setup` command has been removed. You can now re-use the functionality provided by the `tkn-pac setup` command by using the `tkn-pac webhook add` and `tkn-pac webhook update-token` commands. You can use the `tkn-pac webhook add` command to re-add a webhook to an existing Git repository. You can use the `tkn-pac webhook update-token` command to update the personal provider access token for an existing Secret object in the Git repository.	
+* With this update, the `tkn-pac setup` command has been removed. Instead, use the `tkn-pac webhook add` command to re-add a webhook to an existing Git repository. And use the `tkn-pac webhook update-token` command to update the personal provider access token for an existing Secret object in the Git repository.
+
+* With this update, a namespace that runs a pipeline with default settings does not apply the `pod-security.kubernetes.io/enforce:privileged` label to a workload.
+
 
 [id="deprecated-features-1-9_{context}"]	
 == Deprecated and removed features	
@@ -279,7 +287,7 @@ Workaround: Set the `NO_COLOR` environment variable to `true`.
 
 * Running the `tkn pac resolve -f <filename> | oc create -f` command may not provide expected results, if the `tkn pac resolve` command uses a templated parameter value to function.	
 +	
-Workaround: To mitigate this issue, save the output of `tkn pac resolve` in a temporary file by running the `tkn pac resolve -f <filename> -o tempfile.yaml` command and then run the `oc create -f tempfile.yaml` command. For example, `tkn pac resolve -f <filename> -o /tmp/pull-request-resolved.yaml && kubectl create -f /tmp/pull-request-resolved.yaml`.	
+Workaround: To mitigate this issue, save the output of `tkn pac resolve` in a temporary file by running the `tkn pac resolve -f <filename> -o tempfile.yaml` command and then run the `oc create -f tempfile.yaml` command. For example, `tkn pac resolve -f <filename> -o /tmp/pull-request-resolved.yaml && oc create -f /tmp/pull-request-resolved.yaml`.	
 
 [id="fixed-issues-1-9_{context}"]	
 == Fixed issues	
@@ -292,11 +300,24 @@ Workaround: To mitigate this issue, save the output of `tkn pac resolve` in a te
 * Before this update, if duplicate secrets were present in a service account for a pipelines run, it resulted in failure in task pod creation. With this update, this issue is resolved and the task pod is created successfully even if duplicate secrets are present in a service account.	
 // Vincent Demeester	
 
-* Before this update, by looking at the TaskRun's `spec.StatusMessage` field, users could not distinguish whether the `TaskRun` had been cancelled by the user or by a `PipelineRun` that was part of it. With this update, this issue is resolved and users can distinguish the status of the `TaskRun` by looking at the TaskRun's `spec.StatusMessage` field.	
+* Before this update, by looking at the TaskRun's `spec.StatusMessage` field, users could not distinguish whether the `TaskRun` had been cancelled by the user or by a `PipelineRun` that was part of it. With this update, this issue is resolved and users can distinguish the status of the `TaskRun` by looking at the TaskRun's `spec.StatusMessage` field.
 // Vincent Demeester	
 
 * Before this update, webhook validation was removed on deletion of old versions of invalid objects. With this update, this issue is resolved.	
-// Vincent Demeester @vdeemester	
+// Vincent Demeester @vdeemester
+
+* Before this update, if you set the `timeouts.pipeline` parameter to `0`, you could not set the `timeouts.tasks` parameter or the `timeouts.finally` parameters. This update resolves the issue. Now, when you set the `timeouts.pipeline` parameter value, you can set the value of either the`timeouts.tasks` parameter or the `timeouts.finally` parameter. For example:
++
+[source,yaml]
+----
+yaml
+kind: PipelineRun
+spec:
+  timeouts:
+    pipeline: "0"  # No timeout
+    tasks: "0h3m0s"
+----
+// Vincent Demeester @vdeemester
 
 * Before this update, a race condition could occur if another tool updated labels or annotations on a PipelineRun or TaskRun. With this update, this issue is resolved and you can merge labels or annotations.	
 // Vincent Demeester @vdeemester	
@@ -317,7 +338,7 @@ Workaround: To mitigate this issue, save the output of `tkn pac resolve` in a te
 // https://github.com/tektoncd/cli/pull/1557	
 // Piyush Garg @piyush-garg	
 
-* Before this update, if the parent pipelinerun was running while deleting TaskRuns, then TaskRuns would be deleted. With this update, this issue is resolved and TaskRuns are not getting deleted if the parent PipelineRun is running.	
+* Before this update, if the parent PipelineRun was running while deleting TaskRuns, then TaskRuns would be deleted. With this update, this issue is resolved and TaskRuns are not getting deleted if the parent PipelineRun is running.	
 // https://github.com/tektoncd/cli/pull/1736	
 // Piyush Garg @piyush-garg