The previous image was built for amd64 only, which makes any image
using it as base image (such as the resolvers one) also only
targeting amd64.

Signed-off-by: Vincent Demeester <[email protected]>

…nning_pipelineruns metric

The running_pipelineruns metric incorrectly counted pending PipelineRuns
as running. Add !pr.IsPending() check to exclude them.

Fixes #8949

Signed-off-by: divyansh42 <[email protected]>

This disables the Gitea e2e tests temporarily to unblock
temporarily. Gitea chart has changed. We are working to include
that soon.

This code checks if all containers in a Pod, including init containers, have
completed their execution before marking a TaskRun as complete when kubernetes
native sidecar is enabled. It's part of the TaskRun status determination logic.

Signed-off-by: Priti Desai <[email protected]>

…quotas

In case of the PVC creation (from volumeclaimtemplate) is due to a
quota error (quota exceeded), do not fail with a permanent error, and
instead mark the PipelineRun as pending. Once there is some quota
available back, it will be able to start.

Signed-off-by: Vincent Demeester <[email protected]>

Co-authored-by: Stanislav Jakuschevskij <[email protected]>

Similar to issue #8824 for PipelineRuns, the webhook was denying
finalizer updates on completed TaskRuns. The validation webhook was
blocking all updates when TaskRun.IsDone() returned true, preventing
tools like Tekton Chains from clearing finalizers.

To ensure we don't have old obj default drift, we are adding
a fast path check for spec equality and are normalizing the old spec
with current defaults before comparison. Then we allow updates when
only finalizers differ and reject spec changes.

This mirrors the fix applied to PipelineRun validation.

fixes issue #8824 where webhook denied finalizer updates on completed
PipelineRuns. The validation webhook was blocking all updates when
PipelineRun.IsDone() returned true, preventing from
clearing finalizers

to make sure that we don't have old obj default drift we are adding
a fast path check for spec equality and are normalizing the old spec
with current defaults before comparison. Then we allow updates when
only finalizers differ and reject spec changes

Signed-off-by: Vibhav Bobade <[email protected]>

added strings package import to v1/pipelinerun_validation_test.go and v1beta1/pipelinerun_validation_test.go
replaced all t.Context() calls with context.Background() in test files (this method doesn't exist in the testing package)
removed TestPipelineRunTaskRunSpecTimeout_Validate from both v1 and v1beta1 test files as it referenced a non-existent Timeout field in PipelineTaskRunSpec