Pipelines 1.6.3 Release Notes

content

peer review

peer review comments

peer review

rolfe's comments

Author: Souvik Sarkar

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

@@ -77,7 +77,7 @@ The `keep` and `keep-since` annotations are mutually exclusive. For any resource
 
 * Administrators can disable the creation of the `pipeline` service account for the entire cluster, and prevent privilege escalation by misusing the associated SCC, which is very similar to `anyuid`.
 
-* You can now configure feature flags and components by using the `TektonConfig` custom resource, and the custom resources for individual components, such as `TektonPipeline` and `TektonTriggers`. This level of granularity is useful for customization and testing of alpha features such as the Tekton OCI bundle for individual components.
+* You can now configure feature flags and components by using the `TektonConfig` custom resource (CR) and the CRs for individual components, such as `TektonPipeline` and `TektonTriggers`. This level of granularity helps customize and test alpha features such as the Tekton OCI bundle for individual components.
 
 * You can now configure optional `Timeouts` field for the `PipelineRun` resource. For example, you can configure timeouts separately for a pipeline run, each task run, and the `finally` tasks.
 
@@ -306,4 +306,29 @@ Error from server (InternalError): Internal error occurred: failed calling webho
 ** For implicit params:
 *** Do not apply the `PipelineSpec` parameters to the `TaskRefs` object.
 *** Disable implicit param behavior for the `Pipeline` objects.
-// https://github.com/tektoncd/pipeline/releases/tag/v0.28.3
+// https://github.com/tektoncd/pipeline/releases/tag/v0.28.3
+
+[id="release-notes-1-6-3_{context}"]
+== Release notes for {pipelines-title} General Availability 1.6.3
+
+[id="fixed-issues-1-6-3_{context}"]
+=== Fixed issues
+
+* Before this update, the {pipelines-title} Operator installed pod security policies from components such as Pipelines and Triggers. However, the pod security policies shipped as part of the components were deprecated in an earlier release. With this update, the Operator stops installing pod security policies from components. As a result, the following upgrade paths are affected:
+** Upgrading from {pipelines-shortname} 1.6.1 or 1.6.2 to {pipelines-shortname} 1.6.3 deletes the pod security policies, including those from the Pipelines and Triggers components.
+** Upgrading from {pipelines-shortname} 1.5.x to 1.6.3 retains the pod security policies installed from components. As a cluster administrator, you can delete them manually.
++
+[NOTE]
+====
+When you upgrade to future releases, the {pipelines-title} Operator will automatically delete all obsolete pod security policies.
+====
+// https://issues.redhat.com/browse/SRVKP-2259
+
+* Before this update, only cluster administrators could access pipeline metrics in the {product-title} console. With this update, users with other cluster roles also can access the pipeline metrics.
+// https://issues.redhat.com/browse/SRVKP-2129
+
+* Before this update, role-based access control (RBAC) issues with the {pipelines-shortname} Operator caused problems upgrading or installing components. This update improves the reliability and consistency of installing various {pipelines-title} components.
+// https://issues.redhat.com/browse/SRVKP-2249
+
+* Before this update, setting the `clusterTasks` and `pipelineTemplates` fields to `false` in the `TektonConfig` CR slowed the removal of cluster tasks and pipeline templates. This update improves the speed of lifecycle management of Tekton resources such as cluster tasks and pipeline templates.
+// https://issues.redhat.com/browse/SRVKP-2043