You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/op-release-notes-1-11.adoc
+55-23Lines changed: 55 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Before upgrading to the {pipelines-title} Operator 1.11, ensure that you have at
24
24
25
25
* This update adds support for results, object parameters, array results, and indexing into an array when you set the `enable-api-fields` feature flag to `beta` value in the `TektonConfig` CR.
26
26
27
-
* With this update, propagated parameters are now part of a stable feature. This feature enables interpolating parameters in embedded specifications to reduce verbosity in Tekton resources.
27
+
* With this update, propagated parameters are now part of a stable feature. This feature enables interpolating parameters in embedded specifications to reduce verbosity in Tekton resources.
28
28
29
29
* With this update, propagated workspaces are now part of a stable feature. You can enable the propagated workspaces feature by setting the `enable-api-fields` feature flag to `alpha` or `beta` value.
30
30
@@ -41,7 +41,7 @@ Before upgrading to the {pipelines-title} Operator 1.11, ensure that you have at
41
41
42
42
* With this update, you can define and use a `PipelineRun` context variable in the `pipelineRun.workspaces.subPath` configuration.
43
43
44
-
* With this update, the `ClusterResolver`, `BundleResolver`, `HubResolver`, and `GitResolver` features are now available by default.
44
+
* With this update, the `ClusterResolver`, `BundleResolver`, `HubResolver`, and `GitResolver` features are now available by default.
45
45
46
46
47
47
[id="triggers-new-features-1-11_{context}"]
@@ -56,7 +56,7 @@ Before upgrading to the {pipelines-title} Operator 1.11, ensure that you have at
56
56
57
57
* With this update, you can configure pruning for each `PipelineRun` or `TaskRun` resource by setting a `prune-per-resource` boolean field in the `TektonConfig` CR. You can also configure pruning for each `PipelineRun` or `TaskRun` resource in a namespace by adding the `operator.tekton.dev/prune.prune-per-resource=true` annotation to that namespace.
58
58
59
-
* With this update, if there are any changes in the {product-title} cluster-wide proxy, Operator Lifecycle Manager (OLM) recreates the {pipelines-title} Operator.
59
+
* With this update, if there are any changes in the {product-title} cluster-wide proxy, Operator Lifecycle Manager (OLM) recreates the {pipelines-title} Operator.
60
60
* With this update, you can disable the pruner feature by setting the value of the `config.pruner.disabled` field to `true` in the `TektonConfig` CR.
61
61
62
62
@@ -65,7 +65,7 @@ Before upgrading to the {pipelines-title} Operator 1.11, ensure that you have at
65
65
66
66
* With this update, {tekton-chains} is now generally available for use.
67
67
68
-
* With this update, you can use the skopeo tool with {tekton-chains} to generate keys, which are used in the `cosign` signing scheme.
68
+
* With this update, you can use the skopeo tool with {tekton-chains} to generate keys, which are used in the `cosign` signing scheme.
69
69
70
70
* When you upgrade to the {pipelines-title} Operator 1.11, the previous {tekton-chains} configuration will be overwritten and you must set it again in the `TektonConfig` CR.
With this command, you can also specify a custom GitHub API URL by using the `--github-api-url` argument.
104
104
105
-
* This update enables error detection for all `PipelineRun` resources by default. {pac} detects if a `PipelineRun` resource execution has failed and shows a snippet of the last few lines of the error. For a GitHub application, {pac} detects error messages in the container logs and exposes them as annotations on a pull request.
105
+
* This update enables error detection for all `PipelineRun` resources by default. {pac} detects if a `PipelineRun` resource execution has failed and shows a snippet of the last few lines of the error. For a GitHub application, {pac} detects error messages in the container logs and exposes them as annotations on a pull request.
106
106
107
107
* With this update, you can fetch tasks from a private {tekton-hub} instance attached to a private Git repository. To enable this update, {pac} uses the internal raw URL of the private {tekton-hub} instance instead of using the GitHub raw URL.
108
108
@@ -116,58 +116,58 @@ With this command, you can also specify a custom GitHub API URL by using the `--
116
116
117
117
* With this update, {pac} triggers a CI pipeline for a pull request created by a user who is not an owner, collaborator, or public member or is not listed in the `owner` file but has permission to push changes to the repository.
118
118
119
-
* With this update, the custom console setting allows you to use custom parameters from a `Repository` CR.
119
+
* With this update, the custom console setting allows you to use custom parameters from a `Repository` CR.
120
120
121
121
* With this update, {pac} changes all `PipelineRun` labels to `PipelineRun` annotations. You can use a `PipelineRun` annotation to mark a Tekton resource, instead of using a `PipelineRun` label.
122
122
123
123
* With this update, you can use the `pac-config-logging` config map for watcher and webhook resources, but not for the {pac} controller.
124
124
125
125
126
-
[id="breaking-changes-1-11_{context}"]
127
-
== Breaking changes
126
+
[id="breaking-changes-1-11_{context}"]
127
+
== Breaking changes
128
128
129
129
* This update replaces the `resource-verification-mode` feature flag with a new `trusted-resources-verification-no-match-policy` flag in the pipeline specification.
130
130
131
-
* With this update, you cannot edit the {tekton-chains} CR. Instead, edit the `TektonConfig` CR to configure {tekton-chains}.
131
+
* With this update, you cannot edit the {tekton-chains} CR. Instead, edit the `TektonConfig` CR to configure {tekton-chains}.
132
132
133
133
134
-
[id="deprecated-features-1-11_{context}"]
135
-
== Deprecated and removed features
134
+
[id="deprecated-features-1-11_{context}"]
135
+
== Deprecated and removed features
136
136
137
137
* This update removes support for the `PipelineResource` commands and references from Tekton CLI:
138
138
** Removal of pipeline resources from cluster tasks
139
139
** Removal of pipeline resources from tasks
140
140
** Removal of pipeline resources from pipelines
141
141
** Removal of resource commands
142
-
** Removal of input and output resources from the `clustertask describe` command
142
+
** Removal of input and output resources from the `clustertask describe` command
143
143
144
144
* This update removes support for the `full` embedded status from Tekton CLI.
145
145
146
146
* The `taskref.bundle` and `pipelineref.bundle` bundles are deprecated and will be removed in a future release.
147
147
148
148
* In {pipelines-title} 1.11, support for the `PipelineResource` CR has been removed, use the `Task` CR instead.
149
149
150
-
* In {pipelines-title} 1.11, support for the `v1alpha1.Run` objects has been removed. You must upgrade the objects from `v1alpha1.Run` to `v1beta1.CustomRun` before upgrading to this release.
150
+
* In {pipelines-title} 1.11, support for the `v1alpha1.Run` objects has been removed. You must upgrade the objects from `v1alpha1.Run` to `v1beta1.CustomRun` before upgrading to this release.
151
151
152
152
* In {pipelines-title} 1.11, the `custom-task-version` feature flag has been removed.
153
153
154
154
* In {pipelines-title} 1.11, the `pipelinerun.status.taskRuns` and `pipelinerun.status.runs` fields have been removed along with the `embedded-status` feature flag. Use the `pipelinerun.status.childReferences` field instead.
155
155
156
156
157
-
[id="known-issues-1-11_{context}"]
158
-
== Known issues
157
+
[id="known-issues-1-11_{context}"]
158
+
== Known issues
159
159
160
-
* Setting the `prune-per-resource` boolean field does not delete `PipelineRun` or `TaskRun` resources if they were not part of any pipeline or task.
160
+
* Setting the `prune-per-resource` boolean field does not delete `PipelineRun` or `TaskRun` resources if they were not part of any pipeline or task.
161
161
162
162
* Tekton CLI does not show logs of the `PipelineRun` resources that are created by using resolvers.
163
163
164
-
* When you filter your pipeline results based on the `order_by=created_time+desc&page_size=1` query, you get zero records without any `nextPageToken` value in the output.
164
+
* When you filter your pipeline results based on the `order_by=created_time+desc&page_size=1` query, you get zero records without any `nextPageToken` value in the output.
165
165
166
166
* When you set the value of the `loglevel.pipelinesascode` field to `debug`, no debugging logs are generated in the {pac} controller pod. As a workaround, restart the {pac} controller pod.
167
167
168
168
169
-
[id="fixed-issues-1-11_{context}"]
170
-
== Fixed issues
169
+
[id="fixed-issues-1-11_{context}"]
170
+
== Fixed issues
171
171
172
172
* Before this update, {pac} failed to create a `PipelineRun` resource while detecting the `generateName` field in the `PipelineRun` CR. With this update, {pac} supports providing the `generateName` field in the `PipelineRun` CR.
173
173
@@ -180,11 +180,11 @@ With this command, you can also specify a custom GitHub API URL by using the `--
180
180
** `buckets`
181
181
** `kube-api-qps`
182
182
** `kube-api-burst`
183
-
** `threads-per-controller`
183
+
** `threads-per-controller`
184
184
185
-
* This update fixes the remote bundle resolver to perform a case-insensitive comparison of the `kind` field with the `dev.tekton.image.kind` annotation value in the bundle.
185
+
* This update fixes the remote bundle resolver to perform a case-insensitive comparison of the `kind` field with the `dev.tekton.image.kind` annotation value in the bundle.
186
186
187
-
* Before this update, pods for remote resolvers were terminated because of insufficient memory when you would clone a large Git repository. This update fixes the issue and increases the memory limit for deploying remote resolvers.
187
+
* Before this update, pods for remote resolvers were terminated because of insufficient memory when you would clone a large Git repository. This update fixes the issue and increases the memory limit for deploying remote resolvers.
188
188
189
189
* With this update, task and pipeline resources of `v1` type are supported in remote resolution.
190
190
@@ -202,4 +202,36 @@ With this command, you can also specify a custom GitHub API URL by using the `--
202
202
203
203
* Before this update, a long pipeline run would be stuck in the running state on the cluster, even after the timeout. This update fixes the issue.
204
204
205
-
* This update fixes the `tkn pr delete` command for correctly using the `keep` flag. Now, if the value of the `keep` flag equals the number of associated task runs or pipeline runs, the `tkn pr delete` command returns exit code `0` along with a message.
205
+
* This update fixes the `tkn pr delete` command for correctly using the `keep` flag. With this update, if the value of the `keep` flag equals the number of associated task runs or pipeline runs, the `tkn pr delete` command returns exit code `0` along with a message.
206
+
207
+
[id="release-notes-1-11-1_{context}"]
208
+
== Release notes for {pipelines-title} General Availability 1.11.1
209
+
210
+
With this update, {pipelines-title} General Availability (GA) 1.11.1 is available on {product-title} 4.12 and later versions.
211
+
212
+
[id="fixed-issues-1-11-1_{context}"]
213
+
=== Fixed issues
214
+
215
+
* Before this update, a task run could fail with a mount path error message, when a running or pending pod was preempted. With this update, a task run does not fail when the cluster causes a pod to be deleted and re-created.
216
+
217
+
* Before this update, a shell script in a task had to be run as root. With this update, the shell script image has the non-root user ID set so that you can run a task that includes a shell script, such as the `git-clone` task, as a non-root user within the pod.
218
+
219
+
* Before this update, in {pipelines-title} 1.11.0, when a pipeline run is defined using {pac}, the definition in the Git repository references the `tekton.dev/v1beta1` API version and includes a `spec.pipelineRef.bundle` entry, the `kind` parameter for the bundle reference was wrongly set to `Task`. The issue did not exist in earlier versions of {pipelines-title}. With this update, the `kind` parameter is set correctly.
220
+
221
+
* Before this update, the `disable-ha` flag was not correctly passed to the `tekton-pipelines` controller, so the High Availability (HA) feature of {pipelines-title} could not be enabled. With this update, the `disable-ha` flag is correctly passed and you can enable the HA feature as required.
222
+
223
+
* Before this update, you could not set the URL for {tekton-hub} and {artifact-hub} for the hub resolver, so you could use only the preset addresses of {tekton-hub} and {artifact-hub}. With this update, you can configure the URL for {tekton-hub} and {artifact-hub} for the hub resolver, for example, to use a custom {tekton-hub} instance that you installed.
224
+
225
+
* With this update, the SHA digest of the `git-init` image corresponds to version 1.10.5, which is the current released version of the image.
226
+
227
+
* Before this update, the `tekton-pipelines-controller` component used a config map named `config-leader-election`. This name is the default value for knative controllers, so the configuration process for {pipelines-shortname} could affect other controllers and vice versa. With this update, the component uses a unique config name, so the configuration process for {pipelines-shortname} does not affect other controllers and is not affected by other controllers.
228
+
229
+
* Before this update, when a user without write access to a GitHub repository opened a pull request, {pac} CI/CD actions would show as `skipped` in GitHub. With this update, {pac} CI/CD actions are shown as `Pending approval` in GitHub.
230
+
231
+
* Before this update, {pac} ran CI/CD actions for every pull request into a branch that matched a configured branch name. With this update, {pac} runs CI/CD actions only when the source branch of the pull request matches the exact configured branch name.
232
+
233
+
* Before this update, metrics for the {pac} controller were not visible in the {product-title} developer console. With this update, metrics for the {pac} controller are displayed in the developer console.
234
+
235
+
* Before this update, in {pipelines-title} 1.11.0, the Operator always installed {tekton-chains} and you could not disable installation of the {tekton-chains} component. With this update, you can set the value of the `disabled` parameter to `true` in the `TektonConfig` CR to disable installation okindf {tekton-chains}.
236
+
237
+
* Before this update, if you configured {tekton-chains} on an older version of {pipelines-shortname} using the `TektonChain` CR and then upgraded to {pipelines-shortname} version 1.11.0, the configuration information was overwritten. With this update, if you upgrade from an older version of {pipelines-shortname} and {tekton-chains} was configured in the same namespace where the `TektonConfig` is installed (`openshift-pipelines`), {tekton-chains} configuration information is preserved.
0 commit comments