Tags: ernesgonzalez33/pipeline
Tags
tekton: fix KO_CONFIG_PATH on release pipeline - Export the `KO_CONFIG_PATH` variable 🤦 - Using KO_CONFIG_PATH pointing to a file doesn't seem to work with ko 0.12.0 (ko-build/ko#919) Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Bump HorizontalPodAutoscaler apiVersion to v2 Before this, we get a warning when applying the HPA: Warning: autoscaling/v2beta1 HorizontalPodAutoscaler is deprecated in v1.22+, unavailable in v1.25+; use autoscaling/v2 HorizontalPodAutoscaler This also bumps the min version to 1.23. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
Write TaskRun.Status.TaskSpec with replaced spec on every reconcile run fixes tektoncd#5574 With tektoncd#5537, the call to `applyParamsContextsResultsAndWorkspaces` and setting of `tr.Status.TaskSpec` to the output of that call was moved from happening with every call to `reconcile` to only happening if there wasn't already a pod created. This didn't cause any problems with execution, but it sometimes resulted in `tr.Status.TaskSpec` not getting set properly or getting reset to `nil` on a subsequent `reconcile` run, with the end result that, sometimes, `tr.Status.TaskSpec` would contain the original `TaskSpec` without parameter, result, context, and workspace references being replaced with the corresponding value. This caused flaky failures in the `TestPipelineRunStatusSpec/pipeline_status_spec_updated` e2e test, and integration test failures in Chains (tektoncd/chains#577). This change moves the PVC creation out of the `if pod == nil {` block that creates the pod if needed, while still checking if `pod` is `nil` before creating the PVC, and brings the `applyParamsContextsResultsAndWorkspaces` call and setting of `tr.Status.TaskSpec` back out of the pod creation block, but after the possible PVC creation. Signed-off-by: Andrew Bayer <andrew.bayer@gmail.com>
Fix taskrun not working with workspace having volumeClaimTemplate This will move the auto name generation of workspace to happen after the pvc is created for volumeClaimTemplate and then name will be generated for workspace of volumeClaimTemplate type Added an example Fix tektoncd#5537
PreviousNext