|
| 1 | +// This module is included in the following assemblies: |
| 2 | +// * release_notes/op-release-notes-1-17.adoc |
| 3 | + |
| 4 | +:_mod-docs-content-type: REFERENCE |
| 5 | +[id="op-release-notes-1-17_{context}"] |
| 6 | += Release notes for {pipelines-title} General Availability 1.17 |
| 7 | + |
| 8 | +With this update, {pipelines-title} General Availability (GA) 1.17 is available on {OCP} 4.15 and later versions. |
| 9 | + |
| 10 | +[id="new-features-1-17_{context}"] |
| 11 | +== New features |
| 12 | + |
| 13 | +In addition to fixes and stability improvements, the following sections highlight what is new in {pipelines-title} 1.17: |
| 14 | + |
| 15 | +[id="pipelines-new-features-1-17_{context}"] |
| 16 | +=== Pipelines |
| 17 | + |
| 18 | +* With this release, you can configure multiple Git providers by using the Git resolver, or you can add multiple configurations for the same Git provider, in the `TektonConfig` custom resource (CR). You can then specify a Git configuration to use in different task runs and pipeline runs by using the `configKey` parameter. |
| 19 | ++ |
| 20 | +.Example of multiple Git provider configurations |
| 21 | +[source,yaml] |
| 22 | +---- |
| 23 | +apiVersion: operator.tekton.dev/v1alpha1 |
| 24 | +kind: TektonConfig |
| 25 | +metadata: |
| 26 | + name: config |
| 27 | +spec: |
| 28 | +# ... |
| 29 | + pipeline: |
| 30 | + git-resolver-config: |
| 31 | + # configuration 1 |
| 32 | + fetch-timeout: "1m" |
| 33 | + default-url: "https://github.com/tektoncd/catalog.git" |
| 34 | + default-revision: "main" |
| 35 | + scm-type: "github" |
| 36 | + server-url: "" |
| 37 | + api-token-secret-name: "" |
| 38 | + api-token-secret-key: "" |
| 39 | + api-token-secret-namespace: "default" |
| 40 | + default-org: "" |
| 41 | + # configuration 2 |
| 42 | + test1.fetch-timeout: "5m" |
| 43 | + test1.default-url: "" |
| 44 | + test1.default-revision: "stable" |
| 45 | + test1.scm-type: "github" |
| 46 | + test1.server-url: "api.internal-github.com" |
| 47 | + test1.api-token-secret-name: "test1-secret" |
| 48 | + test1.api-token-secret-key: "token" |
| 49 | + test1.api-token-secret-namespace: "test1" |
| 50 | + test1.default-org: "tektoncd" |
| 51 | + # configuration 3 |
| 52 | + test2.fetch-timeout: "10m" |
| 53 | + test2.default-url: "" |
| 54 | + test2.default-revision: "stable" |
| 55 | + test2.scm-type: "gitlab" |
| 56 | + test2.server-url: "api.internal-gitlab.com" |
| 57 | + test2.api-token-secret-name: "test2-secret" |
| 58 | + test2.api-token-secret-key: "pat" |
| 59 | + test2.api-token-secret-namespace: "test2" |
| 60 | + test2.default-org: "tektoncd-infra" |
| 61 | +# ... |
| 62 | +---- |
| 63 | ++ |
| 64 | +.Example of using a `test1` configuration in a pipeline run |
| 65 | +[source,yaml] |
| 66 | +---- |
| 67 | +apiVersion: tekton.dev/v1 |
| 68 | +kind: PipelineRun |
| 69 | +metadata: |
| 70 | + name: example |
| 71 | +spec: |
| 72 | + pipelineRef: |
| 73 | + resolver: git |
| 74 | + params: |
| 75 | + # ... |
| 76 | + - name: configKey |
| 77 | + value: test1 |
| 78 | +# ... |
| 79 | +---- |
| 80 | + |
| 81 | +* With this update, you can now monitor the running `PipelineRun` resources at the namespace, pipeline, and pipeline run level, in addition to the cluster level. You can configure the level through the `TektonConfig` custom resource by setting the `metrics.running-pipelinerun.level` parameter value to `namespace`, `pipeline`, or `pipelinerun`. The default value is empty, which sets the monitoring at cluster level. |
| 82 | ++ |
| 83 | +.Example of monitoring the running pipeline run at the namespace level |
| 84 | +[source,yaml] |
| 85 | +---- |
| 86 | +apiVersion: operator.tekton.dev/v1alpha1 |
| 87 | +kind: TektonConfig |
| 88 | +metadata: |
| 89 | + name: config |
| 90 | +spec: |
| 91 | + pipeline: |
| 92 | + # ... |
| 93 | + metrics.running-pipelinerun.level: namespace |
| 94 | +# ... |
| 95 | +---- |
| 96 | + |
| 97 | +[id="operator-new-features-1-17_{context}"] |
| 98 | +=== Operator |
| 99 | + |
| 100 | +* With this update, you can run the `skopeo-copy` command with additional arguments, for example, `--all` and `--preserve-digests`. You can pass these arguments as a space-separated string, as shown in the following example: |
| 101 | ++ |
| 102 | +.Example command |
| 103 | +[source,terminal] |
| 104 | +---- |
| 105 | +$ tkn task start skopeo-copy -p ARGS="--all --preserve-digests" |
| 106 | +---- |
| 107 | + |
| 108 | +[id="pac-new-features-1-17_{context}"] |
| 109 | +=== {pac} |
| 110 | + |
| 111 | +* With this update, the `pipelines_as_code_running_pipelineruns_count` metric is added to show the number of running `PipelineRun` resources in {pac}. The metric can be filtered by repository or by namespace. |
| 112 | + |
| 113 | +* With this update, the `pipelines_as_code_pipelinerun_duration_seconds_sum` metric is added to show the total duration in seconds taken by all `PipelineRun` resources in {pac}. The metric can be filtered by repository, namespace, `PipelineRun` status, and `PipelineRun` status change reason. |
| 114 | + |
| 115 | +[id="tekton-chains-new-features-1-17_{context}"] |
| 116 | +=== {tekton-chains} |
| 117 | + |
| 118 | +* With this update, you can configure the `TektonConfig` custom resource (CR) to generate the `x509` key pair of the `ecdsa` type and use it with {tekton-chains} to sign artifacts. You can generate the key pair by setting the the `generateSigningSecret` field in the `TektonConfig` custom resource (CR) to `true`: |
| 119 | ++ |
| 120 | +.Example of creating an `ecdsa` key pair |
| 121 | +[source,yaml] |
| 122 | +---- |
| 123 | +apiVersion: operator.tekton.dev/v1 |
| 124 | +kind: TektonConfig |
| 125 | +metadata: |
| 126 | + name: config |
| 127 | +spec: |
| 128 | +# ... |
| 129 | + chain: |
| 130 | + disabled: false |
| 131 | + generateSigningSecret: true |
| 132 | +# ... |
| 133 | +---- |
| 134 | + |
| 135 | +* Before this update, if you did not configure {tekton-chains} in the `TektonConfig` CR, the Operator would not pass any default Chains configuration. |
| 136 | +With this update, if you do not configure {tekton-chains} in the `TektonConfig` CR, the Operator sets the {tekton-chains} configuration with these default properties: |
| 137 | ++ |
| 138 | +[source,yaml] |
| 139 | +---- |
| 140 | +apiVersion: operator.tekton.dev/v1 |
| 141 | +kind: TektonConfig |
| 142 | +metadata: |
| 143 | + name: config |
| 144 | +spec: |
| 145 | +# ... |
| 146 | + chain: |
| 147 | + artifacts.taskrun.format: in-toto |
| 148 | + artifacts.taskrun.storage: oci |
| 149 | + artifacts.oci.storage: oci |
| 150 | + artifacts.oci.format: simplesigning |
| 151 | + artifacts.pipelinerun.format: in-toto |
| 152 | + artifacts.pipelinerun.storage: oci |
| 153 | +# ... |
| 154 | +---- |
| 155 | + |
| 156 | +* With this update, {tekton-chains} now supports extracting the `mongo-server-url` URL from a specified file that can have any name. You can now use the `storage.docdb.mongo-server-url-path` parameter pointing to a valid file path within the container. |
| 157 | + |
| 158 | +[id="breaking-changes-1-17_{context}"] |
| 159 | +== Breaking changes |
| 160 | + |
| 161 | +* With this update, the deprecated `ClusterTask` resource is removed from the Operator. As an alternative, you can use the cluster resolver. |
| 162 | + |
| 163 | +* With this update, the community cluster tasks are removed from the Operator. As an alternative, you can download them from the link:https://github.com/tektoncd/catalog[Tekton catalog] (GitHub resource). The community cluster tasks are planned to be added as tasks in a future release. The following list shows the removed community cluster tasks: |
| 164 | + |
| 165 | +** `argocd-task-sync-and-wait` |
| 166 | +** `git-cli` |
| 167 | +** `helm-upgrade-from-repo` |
| 168 | +** `helm-upgrade-from-source` |
| 169 | +** `jib-maven` |
| 170 | +** `kubeconfig-creator` |
| 171 | +** `pull-request` |
| 172 | +** `trigger-jenkins-job` |
| 173 | + |
| 174 | +[id="fixed-issues-1-17_{context}"] |
| 175 | +== Fixed issues |
| 176 | + |
| 177 | +* With this update, the {pac} controller no longer processes the GitLab push event if the push event payload contains no commit. Instead, it correctly displays an error message warning the user that no commit is attached. |
| 178 | + |
| 179 | +* With this update, the {pac} controller no longer processes the GitLab tag delete event, which caused the controller to crash. Instead, it correctly displays an error message warning the user that deleting the tag event is not supported. |
| 180 | + |
| 181 | +* Before this update, some of the standard variables, header values, and body fields, for example the `body.eventKey` field, were not being resolved in `PipelineRun` resources for the Bitbucket server. With this update, the issue is fixed. |
| 182 | + |
| 183 | +* With this update, the `skopeo-copy` task supports copying multiple images by using the `url.txt` file if the `SOURCE_IMAGE_URL` and `DESTINATION_IMAGE_URL` parameters are left empty. |
| 184 | + |
| 185 | +* Before this update, running the `tkn pac create repo` command on an empty repository resulted in the `.` period symbol being generated as the name of the pipeline run in the template. With this update, the issue is fixed, and the `REPO_NAME.git` is now used as the pipeline run name. |
| 186 | + |
| 187 | +* With this update, the pipeline run failure handling is fixed to accurately report validation failures in the `status.message` field and consistently trigger `finally` tasks, even if a task fails the validation. |
0 commit comments